Understanding the internals of LeakCanary Memory Leak Library in Android.
Narrated by smitnov
smitnov Socials:
YouTube: / @smitnov
Discord: / discord
Twitch: twitch.tv/smitnov
Edited by Atharva Saraf
⭐Join Discord:
/ discord
How LeakCanary works internally?
Part of the Android Internals playlist.
The new LeakCanary library does not need to be initialized by adding LeakCanary.install(this) to the Application. So what is used to automatically initialize following the start of the app?
The principle is to use the feature of ContentProvider to be instantiated with the process startup to achieve unaware initialization
Content providers are loaded before the application class is created.
AppWatchInstaller is a sealed class that inherits ContentProvider.
We understand all the internal details of LeakCanary Memory Leak Library in Android.
Powered by Android Dev Notes
#Android #LeakCanary #AndroidInternals #AndroidDevNotes
References:
https://github.com/square/leakcanary
https://square.github.io/leakcanary/
https://chromium.googlesource.com/ext...
📚 Learn Android from Experts at:
https://github.com/androiddevnotes/aw...
😎 Find more Awesome Android Apps in Kotlin, MVVM, Jetpack:
https://github.com/androiddevnotes/aw...
📑 Android Dev Weekly:
https://github.com/androiddevnotes/an...
📱 Follow us on:
⭐ Discord:
/ discord
⭐ GitHub:
https://github.com/androiddevnotes
⭐ Twitter:
/ androiddevnotes
⭐ Instagram:
/ androiddevnotes
⭐ Blog:
https://codingwithmitch.com/blog/
⭐ Medium:
/ androiddevnotes