Open
Bug 917854
Opened 12 years ago
Updated 3 years ago
[Session Restore] Start counting saveStateDelayed only once saveState is complete.
Categories
(Firefox :: Session Restore, defect)
Firefox
Session Restore
Tracking
()
NEW
People
(Reporter: Yoric, Unassigned)
Details
Theoretically, saveStateDelayed() ensures that we only save the state every ~15 seconds at most. However, if the system is busy, the hard drive is slow or the session state is huge, a non-negligible fraction of this time will be used up by the call to saveState() or the off main thread write.
In such cases, we are going to end up spending a large fraction of the time (and the resources available) just processing and saving the state. In extreme cases, we could be spending all our time doing back-to-back saves of the session state, hence rendering Firefox unusable.
I believe that, to avoid this, we should trigger the timer only after saveState() is complete (including the off main thread write).
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•