Reenable e10s process caching and preallocation for browser_resource_uri.js
Categories
(Core :: DOM: Navigation, defect, P3)
Tracking
()
People
(Reporter: jesup, Unassigned)
References
Details
In bug 1602757 we disabled preallocation and e10s process caching to fix browser_resource_uri.js on windows (only) (the caching was the cause; a push with caching disabled was green). Likely there's some race condition with startup, or something about a process that's been used before that causes an issue. Since process caching/reuse is effectively not used in the field (the process has to have been in use less than 5 seconds), this is reasonable.
This bug is to come back and find out what the issue was and resolve it, then remove the pref setting in browser_resource_uri.js
Updated•5 years ago
|
Comment 1•5 years ago
|
||
The patch from bug 1647470 triggers this on all desktop platforms. With that patch, we reuse an e10s process if it is kept around via dom.ipc.keepProcessesAlive, even when we're under the max process limit.
| Reporter | ||
Updated•4 years ago
|
Description
•