Firefox customers could expertise bugs and points associated to the browser’s Session Restore function whereas Mozilla is engaged on altering the function’s code.
Session Restore is a core function of the Firefox net browser designed to reload the final looking session on begin of the browser.
Firefox customers could arrange the browser to load all open tabs of the earlier looking session on begin of the browser. All that is required for that is to ensure that “Restore earlier session” is enabled on about:preferences.
Mozilla began to work on changing Firefox’s present Session Restore logic to C++ to scale back the function’s impression on the browser’s reminiscence utilization and efficiency.
The bug itemizing on Mozilla’s bug monitoring web site, bug 1474130, highlights the rationale behind the change
content-sessionStore.js is presently loaded into each tab frameloader. Which means it will get loaded a number of instances per course of, which is not nice. But even when loaded solely as soon as, it makes use of about 86Ok. Add to that 17Ok from Content materialRestore.jsm and 12Ok from SessionHistorical past.jsm, and we’re as much as a minimum of 120Ok per course of, if not one of the different helper JSMs get loaded.
The issues that these scripts do can simply be performed by C++ (a few of them extra simply), so there does not appear to be justification for loading this a lot JS into each course of for the sake of session restore.
Ah, and naturally one other 12Ok for Utils.jsm.
Mozilla hopes to handle Sessionstore associated efficiency points with the transfer and to scale back the per-process reminiscence prices of Firefox processes.
The meta Sessionstore function growth bug lists the work that also must be performed to enhance the function. It is clear, simply by trying on the listing of dependencies and open bugs, that it’s going to take fairly a while to resolve all excellent points.
Another meta bug collects reliability reviews associated to Sessionstore, and but another efficiency associated points. The listing of dependencies is even longer and a few customers who filed bugs seen them in steady variations of the Firefox net browser and never growth variations.
Firefox customers will profit from the change as soon as it lands however points could also be skilled within the meantime, particularly in growth variations of the Firefox net browser.
Session Restore could also be unable to revive the session; a minimum of one case has been reported on Reddit by a person who reported that Firefox would restore an older session and never the newest one.
Firefox customers could need to take into account backing up their profiles usually within the meantime or utilizing extensions reminiscent of Session Boss, Tab Stash, SessionSync or Set Aside. (thanks Robert)