Closed
Bug 986145
Opened 11 years ago
Closed 3 years ago
[OS.File] Stop using OS.File during startup
Categories
(Toolkit Graveyard :: OS.File, enhancement)
Toolkit Graveyard
OS.File
Tracking
(Not tracked)
RESOLVED
FIXED
102 Branch
People
(Reporter: Yoric, Unassigned)
References
Details
(Keywords: perf)
Since ChromeWorkers are so slow to start during startup, we need to make sure that any startup-critical OS.File calls are either replaced by something other than OS.File or reimplemented in C++.
Reporter | ||
Comment 1•10 years ago
|
||
Finding out which functions are called during startup is not a simple bug, but it could make a good student project.
Mentor: dteller
Comment 2•4 years ago
|
||
:mconley captured a startup profile that shows usage of OS.File. I'm going to start by filing bugs against the imports in this profile.
Updated•4 years ago
|
Summary: [OS.File] Find out which OS.File functions are called during startup → [OS.File] Stop using OS.File during startup
Reporter | ||
Updated•4 years ago
|
Mentor: dteller
Updated•4 years ago
|
Updated•4 years ago
|
Updated•3 years ago
|
Type: defect → enhancement
Comment 3•3 years ago
|
||
This has been fixed via all the dependencies. Bug 1745459 landed a test change to ensure that osfile.jsm is not loaded before becoming idle.
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → 102 Branch
Updated•3 years ago
|
status-firefox102:
--- → ?
Updated•3 years ago
|
status-firefox102:
? → ---
Updated•2 years ago
|
Product: Toolkit → Toolkit Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•