Detect Memory Leaks with LeakCanary

Re:Detect Memory Leaks with LeakCanary by parth16 on Monday October 19, 2015 @04:15PM (#10415391)

We adopted LeakCanary the day it was released but we don't find it useful at all. In fact, it makes the app almost unusable for us. Every 2-3 mins, it would just freeze the app to capture a heap dump. As our app is quite complicated with a big memory footprint, this just aggravates the problem. I just hope it was more usable.

[ Parent | on HN ]

Re:Detect Memory Leaks with LeakCanary by herbig on Monday October 19, 2015 @04:35PM (#10415530)

I've found LeakCanary incredibly useful at rooting out context related leaks you probably wouldn't otherwise think of.

If you look under "no-op dependency" you'll find a solution to the issue you're describing.

I've found it useful to have a leak canary specific build flavor or type, which only I ever see. For all other debug / production build leak canary is not initialized.

[ Parent | on HN ]