Closed
Bug 591471
Opened 14 years ago
Closed 14 years ago
Modify Talos first-run to allow startupcache to write itself to disk on a timer.
Categories
(Testing :: Talos, defect)
Testing
Talos
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: benedict, Unassigned)
References
Details
Currently, startupcache wants to write itself to disk 10 seconds after startup is complete, so the IO doesn't block startup. In Talos, the browser shuts down immediately after startup, so this write can't happen. The hacky workaround is that startupcache now writes on shutdown as well. The better fix is if Talos first-run doesn't shut down until after startupcache writes out.
Reporter | ||
Comment 1•14 years ago
|
||
Probably not an immediate priority, filing so we don't lose track.
Comment 2•14 years ago
|
||
Is this still a desired change?
Reporter | ||
Comment 3•14 years ago
|
||
dwitte, taras, do we want to keep the startup cache write-on-shutdown? If so, this bug can be closed.
Comment 4•14 years ago
|
||
(In reply to comment #3) > dwitte, taras, do we want to keep the startup cache write-on-shutdown? If so, > this bug can be closed. Yeah I think that's a reasonable behavior.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•