4 ms·
Why writing to disk if firefox is idle and its state doesn't change ? Is it repeatedly rewriting the same data over and over in a storage working like a log dat
by chmike 10y ago
Why writing to disk if firefox is idle and its state doesn't change ? Is it repeatedly rewriting the same data over and over in a storage working like a log database or journal file ?
- Yoric 10y agoUnless there is a bug, Session Restore is not written if Firefox is idle. Of course, many applications are not idle even if you're not using them, and with the current architecture, just one tab using, say, DOM Storage, or updating a session cookie or a hidden form field, is enough to force a rewrite.
- dewiz 10y agoAs an heavy user of session restore and tons of open tabs, I would be OK ignoring updates to tabs that have not been active for a while. For example, let's say I have 10 tabs open but I have been using only the latest tab during the last 5 minutes. In this scenario I don't care about the cookies (eg due to ongoing ajax) nor the state of the other 9 tabs. If the browser crashes I'm OK with those 9 tabs being restored with a 5 minutes old snapshot. So for instance FF should be smart to save the state of new/recent tabs, and should slow down progressively on old/inactive tabs.
- posterboy 10y agodon't generalize your personal use case