For Fragments, these are instances that do not have a valid FragmentManager but are still being referenced. For Activities, these are instances that have been destroyed but are still being referenced. That warning was originally a longer description:Īctivity and Fragment instances that might be causing memory leaks. That's a good question, let's dig into code and figure this out!īefore answering the question, we need to talk about where the idea of false positive leaks comes from: Android Studio. The thing really annoying about LeakCanary or Android Studio, most of the time leaks identified by LeakCanary do not appear in Profiler/Memory/memory leaks, I wonder if LeakCanary is showing false positives or Android Studio is missing positives. I recently came across this comment in a post:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |