Fixed
Status Update
No update yet.
Comments
vi...@google.com
hi...@google.com
For clarity, are you requesting this as a developer or as a user?
vi...@google.com
im tester .. but this bug is confirmed by developer as source bug not ROM..
On Sun, May 14, 2023 at 8:56 PM <buganizer-system@google.com> wrote:
On Sun, May 14, 2023 at 8:56 PM <buganizer-system@google.com> wrote:
vi...@google.com
Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:
What steps are needed to reproduce this issue? Frequency of occurrence?
Which device did you use to reproduce this issue?
Can you confirm if this issue is reproducible on a Pixel/Nexus device?
Screen Record of the Issue
Please capture screen record or video of the issue using following steps:
adb shell screenrecord /sdcard/video.mp4
Subsequently use following command to pull the recorded file:
adb pull /sdcard/video.mp4
Attach the file to this issue.
Android bug report (to be captured after reproducing the issue)
For steps to capture a bug report, please refer:https://developer.android.com/studio/debug/bug-report#bugreportdevice
Alternate method
Navigate to “Developer options”, ensure “USB debugging” is enabled, then enable “Bug report shortcut”. Capture bug report by holding the power button and selecting the “Take bug report” option.
Note: Please upload the bug report and screenshot to google drive and share the folder to android-bugreport@google.com, then share the link here.
What steps are needed to reproduce this issue? Frequency of occurrence?
Which device did you use to reproduce this issue?
Can you confirm if this issue is reproducible on a Pixel/Nexus device?
Screen Record of the Issue
Please capture screen record or video of the issue using following steps:
adb shell screenrecord /sdcard/video.mp4
Subsequently use following command to pull the recorded file:
adb pull /sdcard/video.mp4
Attach the file to this issue.
Android bug report (to be captured after reproducing the issue)
For steps to capture a bug report, please refer:
Alternate method
Navigate to “Developer options”, ensure “USB debugging” is enabled, then enable “Bug report shortcut”. Capture bug report by holding the power button and selecting the “Take bug report” option.
Note: Please upload the bug report and screenshot to google drive and share the folder to android-bugreport@google.com, then share the link here.
xi...@xiaomi.corp-partner.google.com
Comment has been deleted.
xi...@xiaomi.corp-partner.google.com
-What steps are needed to reproduce this issue? Frequency of occurrence?
this happens almost 3 times of 5 times when u pull notification panel down ..occurs sometimes not all times. u just need to pull notification panel down after and after to see it(while animation scalings is set to 0)
-Which device did you use to reproduce this issue?
Xiaomi Redmi note 4X .. almost every A13 AOSP custom ROMs .. (Lineage OS, CrDroid, VoltageOS, PixelOS, ...)
-Can you confirm if this issue is reproducible on a Pixel/Nexus device?
no its not Google device.. and i dont have Pixel/Nexus to test it
since i flashed Feb build i dont have that issue anymore to take report or video .. but i will flash last one again and will take a video and report. also the screen shots are attached in first post here..
https://drive.google.com/drive/folders/1WMQazgZHaYIocQmFblWhQQphSiyA4pWy
this happens almost 3 times of 5 times when u pull notification panel down ..occurs sometimes not all times. u just need to pull notification panel down after and after to see it(while animation scalings is set to 0)
-Which device did you use to reproduce this issue?
Xiaomi Redmi note 4X .. almost every A13 AOSP custom ROMs .. (Lineage OS, CrDroid, VoltageOS, PixelOS, ...)
-Can you confirm if this issue is reproducible on a Pixel/Nexus device?
no its not Google device.. and i dont have Pixel/Nexus to test it
since i flashed Feb build i dont have that issue anymore to take report or video .. but i will flash last one again and will take a video and report. also the screen shots are attached in first post here..
wi...@gmail.com
update: Video and report zip also added to G-Drive ..
also one thing to mention.. this glitch happens more when no notifications is there.. as u can see now capturing screen is there and this happend 2-3 times but when there is nothing in notification panel it happens more..
also one thing to mention.. this glitch happens more when no notifications is there.. as u can see now capturing screen is there and this happend 2-3 times but when there is nothing in notification panel it happens more..
xi...@xiaomi.corp-partner.google.com
We have shared this with our product and engineering team and will update this issue with more information as it becomes available.
ch...@google.com
Thank you for reporting this issue. We’ve investigated, but unfortunately have not been able to reproduce it with the steps provided. If you are able to reproduce the issue again or have additional information to help us, please open a new issue and add the relevant information along with reference to this issue for context.
xi...@xiaomi.corp-partner.google.com
After the patch was merged, the same problem has not recurred until now, and it should have been resolved. Could you please help close this case? Thank you.
Description
Timestamp: 2023-09-20 15:54:42.089157207+0800
Process uptime: 81400s
ZygotePid: 71075172
Cmdline: /system/bin/surfaceflinger
pid: 934, tid: 2693, name: binder:934_5 >>> /system/bin/surfaceflinger <<<
uid: 1000
tagged_addr_ctrl: 0000000000000001 (PR_TAGGED_ADDR_ENABLE)
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0000000000000004
Cause: null pointer dereference
x0 0000000000000000 x1 0000007c57f10470 x2 0000007d0df2c890 x3 0000000000000005
x4 0000007c57f105e8 x5 0000000000000001 x6 0000007c57f10884 x7 5779616c7265764f
x8 0000000000000001 x9 0000000000000004 x10 0000000000000000 x11 0000007d228f9c40
x12 0000007d228f9c30 x13 000000001ad82ef8 x14 000000001ad82ea8 x15 72f16952f11f2587
x16 0000007d0e5e0b28 x17 0000007d1b7212e0 x18 0000007c5744e000 x19 0000000000000000
x20 0000007c57f10470 x21 b400007c55643000 x22 0000007c57f11000 x23 0000007c57f10870
x24 ffffffffffffffb0 x25 b400007c63ba17a0 x26 0000007c57f106d8 x27 0000007c57f11000
x28 b400007c63ba17f0 x29 0000007c57f10440
lr 0000007d0df980d8 sp 0000007c57f10440 pc 0000007d1b721300 pst 0000000060001000
backtrace:
#00 pc 000000000000f300 /system/lib64/libutils.so (android::RefBase::weakref_type::attemptIncStrong(void const*)+32) (BuildId: cca381e6c23f2201d8aeb44675798c5c)
#01 pc 00000000003980d4 /system/lib64/libsurfaceflinger.so (android::Layer::getFixedTransformHint() const+84) (BuildId: 32d2f6d38bf4232be9796de1ca578b05)
#02 pc 000000000032c8a4 /system/lib64/libsurfaceflinger.so (android::BufferLayer::setTransformHint(android::ui::Transform::RotationFlags)+20) (BuildId: 32d2f6d38bf4232be9796de1ca578b05)
#03 pc 00000000003ec9f8 /system/lib64/libsurfaceflinger.so (android::SurfaceFlinger::addClientLayer(android::sp<android::Client> const&, android::sp<android::IBinder> const&, android::sp<android::Layer> const&, android::wp<android::Layer> const&, bool, unsigned int*)+1064) (BuildId: 32d2f6d38bf4232be9796de1ca578b05)
#04 pc 00000000003f251c /system/lib64/libsurfaceflinger.so (android::SurfaceFlinger::createLayer(android::LayerCreationArgs&, android::sp<android::IBinder>*, android::sp<android::IBinder> const&, int*, android::sp<android::Layer> const&, unsigned int*)+2108) (BuildId: 32d2f6d38bf4232be9796de1ca578b05)
#05 pc 000000000033f830 /system/lib64/libsurfaceflinger.so (android::Client::createSurface(android::String8 const&, unsigned int, unsigned int, int, unsigned int, android::sp<android::IBinder> const&, android::LayerMetadata, android::sp<android::IBinder>*, android::sp<android::IGraphicBufferProducer>*, int*, unsigned int*)+416) (BuildId: 32d2f6d38bf4232be9796de1ca578b05)
#06 pc 00000000000e8d74 /system/lib64/libgui.so (android::BnSurfaceComposerClient::onTransact(unsigned int, android::Parcel const&, android::Parcel*, unsigned int)+436) (BuildId: 9e9ed9576f9488d3141c0cf00e778eb9)
#07 pc 0000000000050a4c /system/lib64/libbinder.so (android::BBinder::transact(unsigned int, android::Parcel const&, android::Parcel*, unsigned int)+236) (BuildId: 3ebe40e5fd787860e32d6a8743231d53)
#08 pc 000000000005bc94 /system/lib64/libbinder.so (android::IPCThreadState::executeCommand(int)+1012) (BuildId: 3ebe40e5fd787860e32d6a8743231d53)
#09 pc 000000000005b7d0 /system/lib64/libbinder.so (android::IPCThreadState::getAndExecuteCommand()+160) (BuildId: 3ebe40e5fd787860e32d6a8743231d53)
#10 pc 000000000005c064 /system/lib64/libbinder.so (android::IPCThreadState::joinThreadPool(bool)+68) (BuildId: 3ebe40e5fd787860e32d6a8743231d53)
#11 pc 000000000008bed8 /system/lib64/libbinder.so (android::PoolThread::threadLoop()+24) (BuildId: 3ebe40e5fd787860e32d6a8743231d53)
#12 pc 0000000000013460 /system/lib64/libutils.so (android::Thread::_threadLoop(void*)+416) (BuildId: cca381e6c23f2201d8aeb44675798c5c)
#13 pc 00000000000fbacc /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+204) (BuildId: 95768e541c682c20709fc11df6431f16)
#14 pc 000000000008e670 /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+64) (BuildId: 95768e541c682c20709fc11df6431f16)
524 void RefBase::weakref_type::incWeak(const void* id)
525 {
526 weakref_impl* const impl = static_cast<weakref_impl*>(this);
527 impl->addWeakRef(id);
528
530 const int32_t c __unused = impl->mWeak.fetch_add(1, //Error location：Impl is empty，
531 std::memory_order_relaxed); //Can we use empty space judgment here to prevent it?
533
534 ALOG_ASSERT(c >= 0, "incWeak called on %p after last weak ref", this);
535 }
Previously mentioned to the case--291130353, you said that this part of the code has been optimized on the U version and has undergone significant changes. If the U version has not been replicated, it will not be processed.
Looking at it now, the probability of recurrence on T is quite high. I would like to ask: Is there any optimization plan for this problem on T at present? Thank you