-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Address current LeakCanary reports #747
Comments
We'll take a look. There appear to be an increasing number of leaks lately. |
I have two new LeakCanary reports with ReportFragment and HomeActivity involved. While the previous reports were "never GCed but no leak detected" reports, this time the reports are "excluded leak" reports. Fenix version: Fenix revision 8b793cd
|
New leaks, again different ones:
|
Now I have STR to reproduce one kind of these leaks:
This works in 100% for me to cause a HomeActivity and a ReportFragment leak. |
The number of leaks increased noticeably - there are now leaks on more places. But I can no longer find the LeakCanary app on my device so I can't share any reports. |
@cadeyrn @colintheshots are these reports still happening? |
@sblatz Yes, LeakCanary is still reporting leaks (build from 7/12, I can test with latest version from master tomorrow). Unfortunately I can't find the LeakCanary app in my apps anymore so I don't know how I can share more details. :-/ |
Retested with latest build from master (revision 95367c2). The following steps still always trigger a leak:
|
I'm not able to reproduce the original LeakCanary report found here. I spent a bit of time playing around with the app and found very few leak reports (when running monkey). I think we should punt on this ticket for now as none of them seem super critical. |
Did you try the steps from here? Because this is still reproducible in 100% for me. |
We'll look at this in a future sprint, since there are fewer reports than when this was first filed and leaks were a huge problem. |
@kbrosnan and @rpappalax can also look into this because getting leak testing into our UI tests is very important. |
There is now also a leak when opening a custom tab and then pressing the back button. |
The leak is still present but with the new LeakCanary version the user interface is finally back so I can share more details. Download .hprof file: |
I can no longer reproduce the reported leaks and #8619 seems to fix some leaks. Maybe it's time to close this issue? Or are there still some known leaks? |
A good follow-up is #4506 to prevent future memory leaks.
What
We have reports of a memory leak and we should fix memory leaks because they lead to out-of-memory crashes.
Impact
If we do not resolve this issue, there's a chance the user crashes. These are easy to detect as shown below.
Acceptance criteria
I got two LeakCanary reports.
I attached a ZIP with the two .hprof files.
archive.zip
Device information
┆Issue is synchronized with this Jira Task
The text was updated successfully, but these errors were encountered: