(In reply to Pulsebot from comment #46) > Backout by agolo...@mozilla.com: > https://hg.mozilla.org/integration/autoland/rev/59ce3da9e504 > Backed out 3 changesets for causing xpc failures @test_subprocess.js.
So it looks like we are facing some bad case of a race condition here. We create `running` spawning a process and then we `connectRunning` with its FDs and get a second `proc` process. There `running.stdout` is `id: 1` and had `fd: 16` when `proc.stdin` is `id: 5` with `fd: 16` which seems to be consistent with the expected behavior of those pipes. It means we have two `InputPipe` that shares the same FD. Upon creation they `fillBuffer` https://searchfox.org/mozilla- central/rev/b1cd7e191ac57f8dfe31806be2539e51843c03eb/toolkit/modules/subprocess/subprocess_common.sys.mjs#295. So both enqueues a `read ` call. Somehow the `pollfd.revents` https://searchfox.org/mozilla- central/rev/b1cd7e191ac57f8dfe31806be2539e51843c03eb/toolkit/modules/subprocess/subprocess_unix.worker.js#569 turns `!= 0`for the `InputPipe` of `id:5` before the `id:1` and so we trigger reading the content of the pipe, which is then not available anymore to `id:1`. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1741074 Title: [snap] chrome-gnome-shell extension fails to detect native host connector To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1741074/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
