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

Samebug tips

  1. ,

    The Throwable class is the superclass of all errors and exceptions in the Java language. You need to explicitly call the dispose() before your application goes out of scope.

Solutions on the web

via GitHub by Amosiper
, 1 year ago
Explicit termination method 'close' not called
via GitHub by lining301
, 1 year ago
Explicit termination method 'close' not called
via GitHub by buitienhd91
, 1 year ago
Explicit termination method 'close' not called
via bing.com by Unknown author, 2 years ago
Explicit termination method 'close' not called
via GitHub by kkocel
, 2 years ago
Explicit termination method 'close' not called
java.lang.Throwable: Explicit termination method 'close' not called	at dalvik.system.CloseGuard.open(CloseGuard.java:180)	at java.io.FileOutputStream.(FileOutputStream.java:89)	at java.io.FileOutputStream.(FileOutputStream.java:72)	at com.android.okhttp.okio.Okio.sink(Okio.java:174)	at com.android.okhttp.internal.io.FileSystem$1.sink(FileSystem.java:49)	at com.android.okhttp.internal.DiskLruCache$Editor.newSink(DiskLruCache.java:876)	at com.android.okhttp.Cache$CacheRequestImpl.(Cache.java:410)	at com.android.okhttp.Cache.put(Cache.java:236)