[gv-junit-fis] Run ContentDelegateMultipleSessionsTest on Fission
Categories
(GeckoView :: Sandboxing, task, P2)
Tracking
(firefox121 fixed)
| Tracking | Status | |
|---|---|---|
| firefox121 | --- | fixed |
People
(Reporter: agi, Assigned: owlish)
References
(Blocks 1 open bug)
Details
(Whiteboard: [fission:android:m2] [geckoview:2022q3][fxdroid])
Attachments
(1 file)
This bug tracks enabling all ContentDelegateMultipleSessionsTest to run on Fission.
|
Reporter | |
Updated•4 years ago
|
|
||
Updated•4 years ago
|
|
||
Comment 1•4 years ago
|
||
Tracking this bug for Android Fission milestone M2 (pass tests with Fission enabled).
|
|
||
Updated•2 years ago
|
|
|
||
Updated•2 years ago
|
|
|
||
Updated•2 years ago
|
|
|
||
Comment 2•2 years ago
|
||
Moving Android Fission bugs to the new GeckoView::Sandboxing component.
|
|
||
Updated•1 year ago
|
|
Assignee | |
Updated•8 months ago
|
|
|
Assignee | |
Updated•8 months ago
|
|
|
Assignee | |
Updated•8 months ago
|
|
||
Updated•8 months ago
|
|
|
Assignee | |
Updated•6 months ago
|
|
|
Assignee | |
Comment 3•5 months ago
|
||
In Fission, when this particular navigation happens, we switch process. It's an expected Fission behavior. However, because we switch process, we can no longer test if multiple sessions sharing the same process receive the onCrash or onKill calls. Originally, the navigation was added to the test to get rid of a race condition, when the first tab would crash while the second was still initializing. That is no longer a danger for this test as it has evolved and now we have lots of things happening between initializing the second session and crashing the first one. So to fix the test, I am removing the navigation to make sure the tab stays in the same content process.
Pushed by istorozhko@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/0408d1b0f762 Remove navigation from crashContentMultipleSessions test r=geckoview-reviewers,boek
|
||
Comment 5•5 months ago
|
||
| bugherder | ||
Description
•