Open
Bug 1349809
Opened 7 years ago
Updated 2 years ago
getElevationRequired janks the parent process by doing IO on the main thread
Categories
(Toolkit :: Application Update, defect, P3)
Tracking
()
People
(Reporter: mstange, Unassigned)
References
Details
(Keywords: perf, perf:responsiveness)
Here's a profile that shows 250ms of jank on the parent process: https://perfht.ml/2o72U6m It shows that nsUpdateService.js is walking directories on the main thread and doing blocking main thread IO. At the very least it should do the IO asynchronously (e.g. using OS.File), better yet the whole directory traversal should happen on a worker thread. This will mean that the elevationRequired field can no longer be a synchronous getter, it'll need to be asynchronous.
Updated•7 years ago
|
Priority: -- → P2
Reporter | ||
Comment 1•5 years ago
|
||
Here's another profile of this happening, this time with 1.7 seconds of jank: https://perfht.ml/2V5wSs9
Whiteboard: [qf]
Updated•5 years ago
|
Whiteboard: [qf] → [qf:p2:responsiveness]
Updated•4 years ago
|
Priority: P2 → P3
Comment 2•3 years ago
|
||
Here's a profile where it blocked my Firefox startup for more than 3s on a fast macbook: https://share.firefox.dev/3nmz1Ow
Whiteboard: [qf:p2:responsiveness] → [qf:p2:responsiveness][fxperf]
Updated•3 years ago
|
Whiteboard: [qf:p2:responsiveness][fxperf] → [qf:p2:responsiveness][fxperf:p2]
Updated•2 years ago
|
Performance Impact: --- → P2
Keywords: perf:responsiveness
Whiteboard: [qf:p2:responsiveness][fxperf:p2] → [fxperf:p2]
Updated•2 years ago
|
Whiteboard: [fxperf:p2]
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•