gsmose.blogg.se

The heap analysis now traverses the heap dump using RandomAccessFile instead of ansferTo() and is now 40% faster on API 23 and 20% faster on newer APIs.Īlso, sticky class GC roots are now deduplicated, which great reduces the memory footprint of LeakCanary on API 23 ( #2324). This is just a first pass, feedback and ideas welcome! Performance improvements ¶ SQLiteDatabase in memory (open or closed, as well as their file path).Large bitmap count (bitmaps with more pixels than 1.1x the pixels on screen).Here’s what you’ll now see in the heap dump metadata: Since we’re parsing the heap to find leaks anyway, we might as well report additional interesting metrics. I built LeakCanary to help fix leaks, but in doing so I accidentally wrote a fairly flexible heap dump parser. Visualize the heap dominators / retained size as a treemap.Īnyway, that’s still very much the future, let’s talk about what’s in 2.9.1 now! New metrics in heap analysis metadata ¶.Multiplatform heap analysis? Analyze a JVM heap dump in your browser?!.Moving heap analysis leak visualisation to a separate single app (written with Compose!) available on the PlayStore.

What are some things you’d like to see in a future LeakCanary 3 version? Tell me on Twitter! 🤔 Documentation issue? Report or edit Change Log ¶ LeakCanary will now crash in release builds Plumber-android is a new artifact that fixes known Android leaks 🚽🔧Īnalyzing leaks from the CLI is easier than ever 🍺 Improved support for data structure internalsĭetecting root views retained after View.onDetachedFromWindow()ĭetecting services retained after Service.onDestroy()Ĭompute retained size within the leak trace

Breaking change: FailTestOnLeakRunListener deleted