Closed
Bug 1016557
Opened 12 years ago
Closed 9 years ago
Google can cause sessionstore.js to grow very large, because of 'storage' causing slowness
Categories
(Firefox :: Session Restore, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 938464
People
(Reporter: alex, Unassigned)
Details
I usually have many tabs, like 200-300, and thought that 4-5 MB sessionstore.js was OK.
But today I tried this addon https://addons.mozilla.org/en-us/firefox/addon/about-sessionstore/ which can show exactly how many memory each tab cost.
So in my log each tab was about 400 bytes, and Google search tabs was 100-500KB each.
The more you search with single tab, the more memory it takes in sessionstore.js file. If you open JSON file - many data are in 'storage' field of that tab entry.
This leads to huge sessionstore.js file.
Have the same findings in FF 34. Wasn't using the addon to see tab cost, but was trying to reduce the size of sessionstore.js. Sessionstore.js has massive sections of code for each google search tab open. Reduced my file from ~4MB to 111KB by closing about 8-10 google tabs. I have previously had this file as high as 12MB and found instability to restore tabs and had to manually restore from FF's own backups.
Comment 2•9 years ago
|
||
yup. Bug 938464
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•