Closed Bug 1850587 Opened 9 months ago Closed 9 months ago

Remote frames and proxies in Android Fission isolateNothing & isolateHighValue

Categories

(GeckoView Graveyard :: Sandboxing, task, P1)

All
Android

Tracking

(firefox119 fixed)

RESOLVED FIXED
119 Branch
Tracking Status
firefox119 --- fixed

People

(Reporter: owlish, Assigned: owlish)

References

Details

(Whiteboard: [fxdroid])

Attachments

(1 file)

Tests and assertions affected:

  • TEST-UNEXPECTED-FAIL | js/xpconnect/tests/mochitest/test_isRemoteProxy.html | frames[1] is a remote proxy if Fission is enabled - got false, expected true
  • TEST-UNEXPECTED-FAIL | js/xpconnect/tests/mochitest/test_isRemoteProxy.html | frames[1].location is a remote proxy if Fission is enabled - got false, expected true
  • TEST-UNEXPECTED-FAIL | dom/bindings/test/test_remoteProxyAsPrototype.html | win is a remote proxy if Fission is enabled - got false, expected true

when run on any Android build with Fission enabled and fission.webContentIsolationStrategy set to 0 or 2.

I compared the log for failure and success (with isolateEverything strategy) and one difference is the presence of these in the success logs:

08-18 19:55:36.293  1659  2101 I ActivityManager: Start proc 28537:org.mozilla.geckoview.test_runner:tab35/u0a62 for service org.mozilla.geckoview.test_runner/org.mozilla.gecko.process.GeckoChildProcessServices$tab35
08-18 19:55:36.295 27549 27576 D ServiceAllocator: org.mozilla.gecko.process.GeckoChildProcessServices$tab35 updateBindings: FOREGROUND priority, 0 importance, 3 successful binds, 0 failed binds, 0 successful unbinds

This bug might be related (or maybe even a dupe) to others (see in See Also)

See Also: → 1850444, 1850429, 1850440
Severity: -- → N/A
Priority: -- → P1

It is somewhat expected that this will fail with these isolation strategies as the code is effectively testing the process allocaiton behaviour of isolateEverything - so the processes won't be remote if isolateNothing or isolateHighValue are selected, meaning the tests will fail.

The logic here: https://searchfox.org/mozilla-central/rev/ddb4ab256d0e0a6bad3cbefa93546656284fa472/js/xpconnect/tests/mochitest/test_isRemoteProxy.html#44-49, should be changed to only expect the value to be true if fission is enabled, and webContentIsolationStrategy is isolateEverything. Same deal with https://searchfox.org/mozilla-central/rev/ddb4ab256d0e0a6bad3cbefa93546656284fa472/dom/bindings/test/test_remoteProxyAsPrototype.html#19.

Thank you Nika! I'll adjust the expectations of these tests

Assignee: nobody → bugzeeeeee
Pushed by istorozhko@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/ddf5a96b8817
Adjust expectations for the tests to account for isolation strategy in Fission r=nika
Status: NEW → RESOLVED
Closed: 9 months ago
Resolution: --- → FIXED
Target Milestone: --- → 119 Branch
Whiteboard: [fxdroid]
Blocks: 1855511
No longer blocks: 1855511
Product: GeckoView → GeckoView Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: