Closed Bug 986145 Opened 10 years ago Closed 2 years ago

[OS.File] Stop using OS.File during startup

Categories

(Toolkit Graveyard :: OS.File, enhancement)

enhancement
Not set
normal

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++.
Finding out which functions are called during startup is not a simple bug, but it could make a good student project.
Mentor: dteller
See Also: → 1408729

: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.

Summary: [OS.File] Find out which OS.File functions are called during startup → [OS.File] Stop using OS.File during startup
Mentor: dteller
Depends on: 1671274
Depends on: 1678415
No longer blocks: 975702
Depends on: 975702
No longer depends on: 1678415
See Also: → 1696659
Depends on: 1703357
Blocks: 1522925
No longer blocks: 1522925
Depends on: 1522925
Depends on: 1735166
Type: defect → enhancement
Depends on: 1733540
Blocks: 1737308
No longer depends on: 1733540
Depends on: 1745459
Depends on: 1769042
No longer depends on: 1769042

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: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 102 Branch
Product: Toolkit → Toolkit Graveyard
You need to log in before you can comment on or make changes to this bug.