java.io.EOFException: null in JadbDevice.pull and SyncTransport.readChunk() when reading file from a device about jadb HOT 6 CLOSED

Thanks for reporting this issue

• Can you reproduce this? E.g. does it happen every time you try?
• Does it happen with all files? Can you try e.g. with a very small file.
• If it only happens with this file, can you share it somehow then I can look into this.

from jadb.

@aaronmagi
Are you sure you not executing multiple commands on device concurrently?

from jadb.

@SKART1 yes we are.

Does JADB not support multi-threaded reading? (or adb for that matter)

I just noticed again today some very interesting behaviour where it looks like the device can not be found when another thread is reading a part of a file and a new thread tries to read from the device as well.

Aaron

from jadb.

Can you post a minimal example that exhibit this behaviour? I tried to download a 15mb file, but it worked fine.

from jadb.

@aaronmagi looks like adb have problems with it (I think adb daemon which is on device, but it may be an adb server issue)

Firstly device should be always connected to only one adb server (not your case - just remind)
Secondly - we have faced problem with simultaneously executing test with (from shell, not jadb):

ADB_SHELL_INSTRUMENT =
            "adb shell am instrument -w \\\n" +
            "-r \\\n" +
            " %s" + " \\\n" +  // arguments
            " %s " + " \\\n"+  //class
            " %s/%s\n";

and reading logcat from device with:

adb logcat > 1.txt

When starting next test - adb client showed that device is offline

Finally - I think that it may be caused by not correctly closed connection, but need more debugging

P.S. As a workaround - not to use adb server simultaneously

from jadb.

Thanks for this @SKART1 . I'll close this issue for now, @aaronmagi if you would like to reopen this issue, could you please first try to reproduce without jadb as described above. If it is indeed a jadb issue, please add some steps to reproduce it.

from jadb.