Skip to content
This repository has been archived by the owner on Sep 2, 2020. It is now read-only.

fb-adb shell sometimes fail with "shell: error in stub: fork: Try again" #64

Open
eliasnaur opened this issue Apr 26, 2018 · 2 comments

Comments

@eliasnaur
Copy link

In an attempt to work around https://issuetracker.google.com/issues/73230216, I replaced the use of adb with fb-adb in the supplied script

#!/bin/bash

while : ; do
        OUTPUT=$(fb-adb -e shell 'echo -n exitcode')
        if [[ ! "$OUTPUT" =~ "exitcode" ]]; then
                echo "invalid adb output: $OUTPUT"
                break
        fi
done

Then I started the emulator (an android-26 x86_64 image) and ran the 6 copies of the shell script. After a few minutes, fb-adb fails with:

fb-adb shell: error in stub: fork: Try again

@tophyr
Copy link
Contributor

tophyr commented Apr 26, 2018

Interesting. Can you try with --transport=unix? By default fb-adb implicitly uses adb shell under the hood and sends data back and forth via stdin and stdout.

I would also be interested in results of the test using fb-adb rcmd instead of fb-adb shell.

@eliasnaur
Copy link
Author

fb-adb -e shell --transport=unix 'echo -n exitcode' gives me:

fb-adb shell: unknown transport unix

The same happens with fb-adb -e rcmd --transport=unix .... Using plain fb-adb -e rcmd /system/bin/echo -n exitcode gives almost the same error as with fb-adb shell:

fb-adb rcmd: error in stub: fork: Try again

I'm on Fedora 27 if it helps.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants