Kill GC/CC timers on content-child-will-shutdown
Categories
(Core :: DOM: Content Processes, task)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox75 | --- | fixed |
People
(Reporter: mccr8, Assigned: mccr8)
References
Details
Attachments
(1 file)
|
(deleted),
text/x-phabricator-request
|
Details |
When content-child-will-shutdown gets signalled, we've begun to shut down the content process. We should kill the GC timers when this happens to avoid shutdown hangs in child processes. I don't know how much it will help in practice.
Basically this just requires tweaking nsJSEnvironmentObserver to listen for content-child-will-shutdown and add that topic to the section of Observer() that handles quit-application. Then test it and hope it doesn't cause other issues.
|
Assignee | |
Updated•5 years ago
|
|
|
Assignee | |
Comment 1•5 years ago
|
||
Hopefully this will reduce the number of shutdown hangs in child processes.
|
||
Comment 3•5 years ago
|
||
| bugherder | ||
|
|
Assignee | |
Comment 4•5 years ago
|
||
It looks like maybe this has reduced the number of shutdown hangs where a GC is ongoing. Also, I looked at some GC shutdown hangs before and after this landed, and I saw some with an IPC shutdown state before, but not after.
Description
•