I am getting java.lang.OutOfMemoryError exceptions thrown at different places in my app as reported by Crashlytics. I can't actually reproduce this on my device. But I'm guessing they are being thrown because of memory leaks. I have tried to use LeakCanary https://github.com/square/leakcanary to help track down these errors, but I found that it is difficult to understand exactly what the error stack traces mean and that tool ends up being difficult to use. Can anyone recommend the best way to track down these types of errors?
1 comment
How to deal with the java.lang.OutOfMemoryError exception? | Heykuki News