Too much time spent in AddonManager startup (260ms on Moto G5)
Categories
(Toolkit :: Add-ons Manager, defect)
Tracking
()
People
(Reporter: mstange, Unassigned)
Details
Profiles: https://perfht.ml/2QtHocL (0.4ms interval) / https://perfht.ml/2xSYRFj (5ms interval - less information, more realistic timings)
During GeckoView startup we spend 260ms in AddonManager startup (on a Moto G5). This code is on the critical path during the "App link" startup scenario.
Together with bug 1620447, this makes up the vast majority of time spent in JS code in the parent process during startup. Unlike bug 1620447, AddonManager startup happens before the content process can be initialized, so it delays the initial page load.
Reporter | ||
Updated•5 years ago
|
Comment 1•5 years ago
|
||
Maybe a duplicate of bug 1356825?
From a brief scan of the second profile in comment 0, it looks like a significant chunk of time is importing OS.File (bug 1522925, bug 1408729)
Reporter | ||
Updated•5 years ago
|
Reporter | ||
Comment 3•5 years ago
|
||
(In reply to Andrew Swan [:aswan] from comment #1)
From a brief scan of the second profile in comment 0, it looks like a significant chunk of time is importing OS.File (bug 1522925, bug 1408729)
Yeah, I agree. Thanks for pointing out those bugs!
Description
•