java.io.IOException: Bad file number

GitHub | VictorJava | 8 months ago
tip
Your exception is missing from the Samebug knowledge base.
Here are the best solutions we found on the Internet.
Click on the to mark the helpful solution and get rewards for you help.
  1. Speed up your debug routine!

    Automated exception search integrated into your IDE

  2. 0

    Android. Uncaught exception thrown by finalizer

    Stack Overflow | 3 years ago | KennyPowers
    java.io.IOException: Bad file number
  3. 0

    ADB Connection Error

    Stack Overflow | 4 years ago | Raveesh Lawrance
    java.io.IOException: An existing connection was forcibly closed by the remote host at sun.nio.ch.SocketDispatcher.read0(Native Method) at sun.nio.ch.SocketDispatcher.read(Unknown Source) at sun.nio.ch.IOUtil.readIntoNativeBuffer(Unknown Source) at sun.nio.ch.IOUtil.read(Unknown Source) at sun.nio.ch.SocketChannelImpl.read(Unknown Source) at com.android.ddmlib.AdbHelper.executeRemoteCommand(AdbHelper.java:395) at com.android.ddmlib.Device.executeShellCommand(Device.java:462) at com.android.ddmuilib.logcat.LogCatReceiver$1.run(LogCatReceiver.java:110)

    1 unregistered visitors
    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. java.io.IOException

      Bad file number

      at android.net.LocalSocketImpl.close_native()
    2. Android Platform
      LocalSocketImpl.finalize
      1. android.net.LocalSocketImpl.close_native(Native Method)
      2. android.net.LocalSocketImpl.close(LocalSocketImpl.java:225)
      3. android.net.LocalSocketImpl.finalize(LocalSocketImpl.java:487)
      3 frames
    3. Java RT
      Thread.run
      1. java.lang.Daemons$FinalizerDaemon.doFinalize(Daemons.java:187)
      2. java.lang.Daemons$FinalizerDaemon.run(Daemons.java:170)
      3. java.lang.Thread.run(Thread.java:856)
      3 frames