Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via GitHub by coldneverdie
, 1 year ago
Couldn't dump heap; open("/storage/emulated/0/Download/leakcanary/suspected_leak_heapdump.hprof") failed: No such file or directory
via GitHub by bywyu
, 2 years ago
via GitHub by jeslec
, 2 years ago
Failure during heap dump; check log output for details
via GitHub by Maragues
, 2 years ago
Failure during heap dump; check log output for details
via GitHub by Awent
, 2 years ago
Failure during heap dump; check log output for details
via Stack Overflow by jureispro
, 2 years ago
Failure during heap dump; check log output for details
java.lang.RuntimeException: Couldn't dump heap; open("/storage/emulated/0/Download/leakcanary/suspected_leak_heapdump.hprof") failed: No such file or directory	at dalvik.system.VMDebug.dumpHprofData(Native Method)	at dalvik.system.VMDebug.dumpHprofData(VMDebug.java:302)	at android.os.Debug.dumpHprofData(Debug.java:1775)	at com.squareup.leakcanary.AndroidHeapDumper.dumpHeap(AndroidHeapDumper.java:69)	at com.squareup.leakcanary.RefWatcher.ensureGone(RefWatcher.java:122)	at com.squareup.leakcanary.RefWatcher$5.run(RefWatcher.java:103)	at android.os.Handler.handleCallback(Handler.java:751)	at android.os.Handler.dispatchMessage(Handler.java:95)	at android.os.Looper.loop(Looper.java:154)	at android.os.HandlerThread.run(HandlerThread.java:61)