Use casesįinally, the moment you’ve been waiting for : memory leak examples 🙂 💡 LeakCanary only detects leaks of the following objects : Activity, Fragment, View and ViewModel.

You can see the full list of known leaks in the AndroidReferenceMatchers class. A library leak is a leak caused by a known bug in 3rd party code that you do not have control over. LeakCanary separates the leaks it finds in your app into two categories: Application Leaks and Library Leaks. Dumping the heap freezes the app for a couple of seconds, during which LeakCanary displays the following toast: hproffile stored in the Android file system. Once the count of retained objects reaches a threshold, LeakCanary dumps the Java heap into a. 💡 The default threshold is 5 retained objects when the app is visible, and 1 retained object when the app is not visible. If the weak reference held by ObjectWatcher is not cleared by the GC after 5 seconds, the watched object is considered retained, and potentially leaking. Then these objects are passed to a specific object called ObjectWatcher, which holds weak references to them. LeakCanary hooks into the Android lifecycle and detects when activities and fragments are destroyed and should be garbage collected. Once installed, LeakCanary automatically detects and reports memory leaks in 4 steps: You can now launch your app and confirm that LeakCanary is running by filtering on the LeakCanary tag in Logcat:ĭ LeakCanary: LeakCanary is running and ready to detect leaks

It’s a ”plug & play” kind of library where the only thing you need to do is to add the leakcanary-android dependency to your app’s adle file: LeakCanary is a memory leak detection library for Android, developed by Square.

An icon for each garbage collection event.

A dashed line indicates the number of allocated objects, as indicated by the y-axis on the right.

A stacked graph of how much memory is being used by each memory category, as indicated by the y-axis on the left and the colour key at the top.

The memory use timeline, which includes the following:.

The event timeline, which shows the activity states, user input events, and screen rotation events.

A button to jump forward to the live memory data.

Buttons to zoom in/out of the timeline.

Selecting the appropriate option may help you improve app performance while profiling.

A dropdown menu to specify how frequently the profiler captures memory allocations.

A button to force a garbage collection event.

How to use android studio profiler