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 Stack Overflow by Gurpreet
, 2 years ago
close failed: EBADF (Bad file number)
via Stack Overflow by Ekam Dz Singh
, 1 year ago
via ezeenow.com by Unknown author, 2 years ago
close failed: EBADF (Bad file number)
via Stack Overflow by VR Vijay
, 2 years ago
close failed: EBADF (Bad file number)
libcore.io.ErrnoException: close failed: EBADF (Bad file number) at libcore.io.Posix.close(Native Method) at libcore.io.BlockGuardOs.close(BlockGuardOs.java:75) at com.android.internal.os.ZygoteInit.closeServerSocket(ZygoteInit.java:221) at com.android.internal.os.ZygoteConnection.handleChildProc(ZygoteConnection.java:879) at com.android.internal.os.ZygoteConnection.runOnce(ZygoteConnection.java:242) at com.android.internal.os.ZygoteInit.runSelectLoop(ZygoteInit.java:713) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:649) at dalvik.system.NativeStart.main(Native Method)