STR:

• Run docshell/test/navigation/test_bug1699721.html on any Android Fission build with isolateNothing or isolateHighValue strategy (set fission.webContentIsolationStrategy to 0 or 2 respectively).
• The test will timeout after printing this message (the next info message never gets printed)

Comparing the logcats of a failing case and a passing case, I see these lines present in the passing log:

08-18 19:31:34.573  1659  1671 I ActivityManager: Start proc 4075:org.mozilla.geckoview.test_runner:tab35/u0a62 for service org.mozilla.geckoview.test_runner/org.mozilla.gecko.process.GeckoChildProcessServices$tab35
08-18 19:31:34.575  3536  3564 D ServiceAllocator: org.mozilla.gecko.process.GeckoChildProcessServices$tab35 updateBindings: FOREGROUND priority, 0 importance, 3 successful binds, 0 failed binds, 0 successful unbinds

and absent in the failing one. So the timeout seems to be related to the process switching behavior when there are popups specifically with isolateNothing or isolateHighValue strategy.

The severity field is not set for this bug.
:kaya, could you have a look please?

For more information, please visit BugBot documentation.

https://hg.mozilla.org/mozilla-central/rev/a2725a121e1f