Awesome library works like magic.

Using it right now on the Tickertape app. It has been crucial for detecting and fixing memory leaks related to Fragments and RecyclerViews. Thanks a lot for making this

Super easy to use.. fantastic library 😍

A one-line dependency with no extra setup - there's no reason why you wouldn't add this library to your debugging toolkit. I've been using LeakCanary in all my personal apps and it's been incredibly helpful -- sometimes even finding leaks in AndroidX libraries. Thanks for contributing to the open-source community PY!

Very very very useful library.
Have used it since the beginning on the main app of the HELLO device.

For an app like ours that is the main app of a device ( kind of like a launcher + lots of other stuff ), and is opened for the most time that the device is plugged in, IF they are leaks, even very little ones, they will after some time add up to OOM.

LeakCanary has caught lots of very interesting and wierd leaks and saved us from many OOMs.

Interesting library! Got to know about a lot of memory leaks from it! It even helped in pointing out a memory leak when using Fragments with Data Binding which could not have caught otherwise. 👏

I love how this lib has become the defacto standard in reporting memory leaks that happens within Google's frameworks. Few weeks ago I reported a memory leak in the navigation component and attached a project and a Leak canary stacktrace as a proof.

Recently it got acknowledged, fixed and will be released in the next version of the lib!

Really awesome library. I really like how much presentable way they show the info to the developer. UX is insanely great and intuitive. And compared to version 1, version 2 is really fast.
I use in Snaps App
and TOEFL App

LeakCanary website is very helpful. Learned a good deal about memory leaks in android thanks to the people writing them about it briefly and with just enough detail.

I see that this website has the potential to become a go to resource for all things memory leaks: cataloging them, linking them with AOSP bugs, sharing best practices, etc.

Thanks a lot @pyricau and everyone contributing to this website.