Keep Fission processes alive in browser/components/uitour/test/
Categories
(Core :: DOM: Content Processes, task, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox72 | --- | fixed |
People
(Reporter: mccr8, Assigned: mccr8)
References
(Blocks 2 open bugs)
Details
Attachments
(1 file)
About a third of the last 100 hangs in bug 1358898 are in the browser/components/uitour/test/ directory. As a work around, I'll try keeping Fission processes alive, as I did in bug 1580212 for another directory.
Assignee | ||
Comment 1•5 years ago
|
||
(This accounts for the failures in mochitest-browser-chrome-fis-e10s-7.)
Assignee | ||
Updated•5 years ago
|
Assignee | ||
Comment 2•5 years ago
|
||
There are a lot of intermittent hangs in this directory when Fission
is enabled. Keeping processes alive should avoid these.
Assignee | ||
Comment 3•5 years ago
|
||
For some reason, the chunk that uitour was showing up in is different than the failures, so it took me a bit to get the right one (bc3), but with this patch I wasn't able to reproduce the shutdown hangs. The rate is a little lower than the other one so it is hard to know for sure if that means it is fixed.
https://treeherder.mozilla.org/#/jobs?repo=try&revision=8b65c545e235e302224daba5435be76b40703105
Comment 5•5 years ago
|
||
bugherder |
Comment 6•5 years ago
|
||
Retroactively moving fixed bugs whose summaries mention "Fission" (or other Fission-related keywords) but are not assigned to a Fission Milestone to an appropriate Fission Milestone.
This will generate a lot of bugmail, so you can filter your bugmail for the following UUID and delete them en masse:
0ee3c76a-bc79-4eb2-8d12-05dc0b68e732
Description
•