Status Update
No update yet.
Comments
ku...@transsion.corp-partner.google.com
Dear Google
On the android T version, when the phone is running monkey, we found that VolumeDialogImpl is leaked in the Offscreen Layers in dump sf.
Layer VolumeDialogImpl#102014 (BufferStateLayer) callingPid:1819 callingUid:1000 ownerUid:10211
VolumeDialogImpl is referenced by the systemui process. If we see VolumeDialogImpl in Offscreen Layers in dumpsys SurfaceFlinger, then this layer is not destructed and released, resulting in leakage.
pls help check，tks
On the android T version, when the phone is running monkey, we found that VolumeDialogImpl is leaked in the Offscreen Layers in dump sf.
Layer VolumeDialogImpl#102014 (BufferStateLayer) callingPid:1819 callingUid:1000 ownerUid:10211
VolumeDialogImpl is referenced by the systemui process. If we see VolumeDialogImpl in Offscreen Layers in dumpsys SurfaceFlinger, then this layer is not destructed and released, resulting in leakage.
pls help check，tks
ku...@transsion.corp-partner.google.com
[Enter a short description of the problem.]
When monkeying, the layer leaks and does not release
DEVICE:Pixel
OS VERSION:Android 13
BUILD-ID:google/flame/flame:13/TP1A.221005.002.B2/9382335:user/release-keys
STEPS TO REPRODUCE: (please be specific)
1.Monkey
2.dumpsys SurfaceFlinger
3.there will be an Offscreen Layers leakage issue in the dumpsys SurfaceFlinger
REPRODUCE RATE:
Must
OBSERVED RESULTS:
layer leaks and does not release
EXPECTED RESULTS:
No layer leaks
REPRODUCIBLE on Pixel/Nexus Devices: Yes
BUG REPORT (Please attach a full bugreport, Logcat isn't enough):
bugreport-flame-TP1A.221005.002.B2-2023-10-01-14-28-23.zip
ADDITIONAL INFORMATION:
Dear Google
On the android T version, when the phone is running monkey, we found that VolumeDialogImpl is leaked in the Offscreen Layers in dump sf.
Layer VolumeDialogImpl#102014 (BufferStateLayer) callingPid:1819 callingUid:1000 ownerUid:10211
VolumeDialogImpl is referenced by the systemui process. If we see VolumeDialogImpl in Offscreen Layers in dumpsys SurfaceFlinger, then this layer is not destructed and released, resulting in leakage.
pls help check，tks
When monkeying, the layer leaks and does not release
DEVICE:Pixel
OS VERSION:Android 13
BUILD-ID:google/flame/flame:13/TP1A.221005.002.B2/9382335:user/release-keys
STEPS TO REPRODUCE: (please be specific)
1.Monkey
2.dumpsys SurfaceFlinger
3.there will be an Offscreen Layers leakage issue in the dumpsys SurfaceFlinger
REPRODUCE RATE:
Must
OBSERVED RESULTS:
layer leaks and does not release
EXPECTED RESULTS:
No layer leaks
REPRODUCIBLE on Pixel/Nexus Devices: Yes
BUG REPORT (Please attach a full bugreport, Logcat isn't enough):
bugreport-flame-TP1A.221005.002.B2-2023-10-01-14-28-23.zip
ADDITIONAL INFORMATION:
Dear Google
On the android T version, when the phone is running monkey, we found that VolumeDialogImpl is leaked in the Offscreen Layers in dump sf.
Layer VolumeDialogImpl#102014 (BufferStateLayer) callingPid:1819 callingUid:1000 ownerUid:10211
VolumeDialogImpl is referenced by the systemui process. If we see VolumeDialogImpl in Offscreen Layers in dumpsys SurfaceFlinger, then this layer is not destructed and released, resulting in leakage.
pls help check，tks
vi...@google.com
li...@gmail.com
Hi!
I've encountered the same issue on Android 11, but I can't access 303943199("Access is denied to this issue").
Could you help me with this?
Thanks!
Description
This form is only for reporting bugs found in the Android system while
developing Android applications. Use the Tools templates for issues with
the developer tools.
Please describe the problem in detail. Be sure to include:
- Steps to reproduce the problem (including sample code if appropriate).
- What happened.
- What you think the correct behavior should be.
Don't forget to mention which version of Android you're using, and/or which
device the problem appears on (model and Android version).
Please also run "adb bugreport" and archive the output.
To avoid the possibility of sharing private information, please share bugreports and screenshots from Google Drive. Share files with android-bugreport@google.com and include only Google drive links in your bug. If attaching bug reports or other sensitive data directly to issues, please mark the attachment(s) as “Restricted (
Disclaimer:
Please note, by submitting this bug report, you acknowledge that Google may use information included in the bug report to diagnose technical issues and to improve our products and services, in accordance with our Privacy Policy (
Bug reports include personal information logged on your device or by apps, such as:
File names
Installed apps and usage
Email addresses of the profiles on the device
Device identifiers, such as phone number
Web history information, including URLs / URIs
Location information, including limited location history
Network information, such as IP/SSID/MAC addresses and saved or scanned APNs
System or device information, such as memory and processes