Obsolete
Status Update
Comments
sa...@google.com <sa...@google.com>
sa...@google.com <sa...@google.com> #2
Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:
1. A sample project and apk to reproduce the issue.
2. 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.
3. Heap dump / hprof file if possible.
1. A sample project and apk to reproduce the issue.
2. 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.
3. Heap dump / hprof file if possible.
dy...@gmail.com <dy...@gmail.com> #3
Hi there,
Attached below, you can find the following files:
- LeakDemo.zip: A demo project able to produce the leak
- app-release.apk: A non-debuggable demo APK
- HeapDump.hprof: The Heap Dump obtained using Leak Canary using a debuggable version of the APK.
I'm afraid I won't be able to provide a bug report. But here's some information that may help you even more:
- Device: Pixel 4 XL
- Android Version: R
- Build Number: RPP2.200227.009
- Fingerprint: google/coral/coral:10/RPP2.200227.009/6291673:user/release-keys
dy...@gmail.com <dy...@gmail.com> #5
Thank you! I will let you know when the next Android R Developer Preview release will be available.
sa...@google.com <sa...@google.com> #6
Thank you for reporting this issue. We were able to reproduce the issue on the public Android R Developer Preview build. However, the issue is not reproducible on our internal development build (which is ahead of the public release). Please test it on the next public release and let us know if you are still having this problem by filing a new issue (also reference this issue for context). Thanks.
Description
Here's the output obtained via LeakCanary:
```
┬───
│ GC Root: System class
│
├─ android.app.ApplicationPackageManager class
│ Leaking: NO (a class is never leaking)
│ ↓ static ApplicationPackageManager.mHasSystemFeatureCache
│ ~~~~~~~~~~~~~~~~~~~~~~
├─ android.app.ApplicationPackageManager$1 instance
│ Leaking: UNKNOWN
│ Anonymous subclass of android.app.PropertyInvalidatedCache
│ ↓ ApplicationPackageManager$1.mCache
│ ~~~~~~
├─ android.app.PropertyInvalidatedCache$1 instance
│ Leaking: UNKNOWN
│ Anonymous subclass of java.util.LinkedHashMap
│ ↓ PropertyInvalidatedCache$1.tail
│ ~~~~
├─ java.util.LinkedHashMap$LinkedHashMapEntry instance
│ Leaking: UNKNOWN
│ ↓ LinkedHashMap$LinkedHashMapEntry.key
│ ~~~
├─ android.app.ApplicationPackageManager$HasSystemFeatureQuery instance
│ Leaking: UNKNOWN
│ ↓ ApplicationPackageManager$HasSystemFeatureQuery.this$0
│ ~~~~~~
├─ android.app.ApplicationPackageManager instance
│ Leaking: UNKNOWN
│ ↓ ApplicationPackageManager.mContext
│ ~~~~~~~~
├─ android.app.ContextImpl instance
│ Leaking: UNKNOWN
│ ↓ ContextImpl.mAutofillClient
│ ~~~~~~~~~~~~~~~
╰→ com.example.app.ui.activities.SplashActivity instance
Leaking: YES (ObjectWatcher was watching this because com.example.app.ui.activities.SplashActivity received Activity#onDestroy() callback and Activity#mDestroyed is true)
key = 6a69a2a3-1d38-4d27-8c4c-cae915bea1b1
watchDurationMillis = 15093
retainedDurationMillis = 10089
METADATA
Build.VERSION.SDK_INT: 29
Build.MANUFACTURER: Google
LeakCanary version: 2.2
App process name:
Analysis duration: 4326 ms
```
My splash screen is just a simple splash screen it doesn't contain anything about Autofill (No EditText views) or anything.
This is a regression from the Android 11 Developer Preview 1 since it was not happening before the DP2.
Note: My package name has been replaced by `