PLEASE READ:

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 (https://developers.google.com/issue-tracker/concepts/restricted-content)” when creating a bug or adding a comment. Restricting or deleting your comment or attachment can also be done using the overflow menu after submitting.

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 (https://policies.google.com/privacy), and you agree that we may share it with engineering partners potentially impacted by your issue.

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

==================================== HEAP ANALYSIS RESULT

1 APPLICATION LEAKS

References underlined with "~~~" are likely causes. Learn more at https://squ.re/leaks.

398539 bytes retained by leaking objects Signature: fb9ada17304cf3ae53938143f328045ed2cda54f ┬─── │ GC Root: Global variable in native code │ ├─ android.credentials.CredentialManager$GetCredentialTransport instance │ Leaking: UNKNOWN │ Retaining 434.5 kB in 4471 objects │ mContext instance of com.bells.user.login.LoginActivity with mDestroyed = true │ CredentialManager$GetCredentialTransport is a binder stub. Binder stubs will often be retained long after the │ associated activity or service is destroyed, as by design stubs are retained until the other side gets GCed. If │ CredentialManager$GetCredentialTransport is not a static inner class then that's most likely the root cause of │ this leak. Make it static. If CredentialManager$GetCredentialTransport is an Android Framework class, file a │ ticket here: https://issuetracker.google.com/issues/new?component=192705 │ ↓ CredentialManager$GetCredentialTransport.mContext │ ~~~~~~~~ ╰→ com.bells.user.login.LoginActivity instance ​ Leaking: YES (ObjectWatcher was watching this because com.bells.user.login.LoginActivity received ​ Activity#onDestroy() callback and Activity#mDestroyed is true) ​ Retaining 398.5 kB in 4070 objects ​ key = 5d390af8-4b04-41d8-baa3-3518fdf897ff ​ watchDurationMillis = 5706 ​ retainedDurationMillis = 702 ​ mApplication instance of com.base.mobile.BaseApplication ​ mBase instance of com.bells.ui.baseview.BaseActivity$1