Open
Bug 1638119
Opened 5 years ago
Updated 1 year ago
Allow extension processes to be preallocated
Categories
(Core :: DOM: Navigation, defect, P3)
Core
DOM: Navigation
Tracking
()
NEW
Performance Impact | medium |
People
(Reporter: jesup, Unassigned)
References
Details
(Keywords: perf:resource-use)
Bug 1602757 adds preallocation of most types of processes; however extension processes fail when preallocated due to code that calls ExtensionPolicyService::IsExtensionProcess() before the remoteType has been set to 'extension'
It would be nice to be able to preallocate extension processes as well to (hopefully) improve startup.
Since we normally have only a single extension process and it's long-lived, this is mostly a startup issue.
Updated•5 years ago
|
Whiteboard: [qf] → [qf:p2:resource]
Updated•4 years ago
|
Severity: -- → S3
Priority: -- → P3
Comment 1•3 years ago
|
||
triaging
jesup is this bug still valid and reflect future work?
Flags: needinfo?(rjesup)
Updated•3 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•