> Richmond wrote:
>> Some time ago, 2016 I think, there was some fuss about the browser
>> session restore interval being 15 seconds, and how this causes SSD to
>> wear out. I noticed recently having put firefox on a tablet that the
>> interval is still 15 seconds. So was anything done about this problem?
> Note the "One thought on ..." comment from Feb 12.
> I can't confirm it, because my FF 52ESR doesn't have the mentioned
> browser.sessionstore.interval.idle setting. Maybe it's only in the
> newer "normal" releases?
That's interesting. I couldn't find documentation for it, except
apparently in the source code. I have the setting in 61.0b6 but I don't
think it was in the android version I have.
I don't think people are likely to change these settings though at the
time they install. They won't be thinking about it.
Where it says:
* Minimal interval between two save operations (in milliseconds).
* To save system resources, we generally do not save changes
* a change is detected. Rather, we wait a little to see if this change is
* followed by other changes, in which case only the last write is
* This delay is defined by "browser.sessionstore.interval".
* Furthermore, when the user is not actively using the computer, webpages
* may still perform changes that require (re)writing to sessionstore, e.g.
* updating Session Cookies or DOM Session Storage, or refreshing, etc. We
* expect that these changes are much less critical to the user and do not
* need to be saved as often. In such cases, we increase the delay to
* When the user returns to the computer, if a save is pending, we
* it to happen soon, with "browser.sessionstore.interval".