googleads / googleads/googleads-mobile-android-examples
appOpenExample - memory leaks!
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.9k
- Forks
- 1.9k
- Avg merge
- 15d 19h
- Merged PRs (30d)
- 1
Description
com.google.android.gms.example.appopenexample.SplashActivity instance
Leaking: YES (ObjectWatcher was watching this because com.google.android.gms.example.appopenexample.
SplashActivity received Activity#onDestroy() callback and Activity#mDestroyed is true)
Retaining 6.3 kB in 208 objects
key = ed77da51-16c3-4079-9d1d-10f1384a06b0
watchDurationMillis = 20022
retainedDurationMillis = 12768
mApplication instance of com.google.android.gms.example.appopenexample.MyApplication
mBase instance of androidx.appcompat.view.ContextThemeWrapper
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the LeakCanary report in the appOpenExample and tracing the com.google.android.gms.example.appopenexample.SplashActivity lifecycle through Activity#onDestroy(). Done means identifying and fixing the retained SplashActivity instance, then verifying that the leak no longer appears after the activity is destroyed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- mobile-dev, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100