XP SP3
SeaMonkey 2.46
Intel e4300
2 GB RAM
Yes XP.
Yes only 2 GB RAM.
Yes a dated computer.
SeaMonkey RAM usage, 1.5 GB.
Yes I do use a LOT of windows/tabs, opened from Session Restore on startup.
2.40 ran fine (within its limits).
2.46, so far does not.
Yes I can (over) push 2.40 to where it ran poorly, but 2.46 runs poorly virtually out of the box.
I'm seeing a lot of this:
Code: Select all
Error: uncaught exception: out of memory
Code: Select all
Error: NS_ERROR_OUT_OF_MEMORY: Component returned failure code: 0x8007000e (NS_ERROR_OUT_OF_MEMORY) [nsIScriptableUnicodeConverter.convertToInputStream]
Source File: resource://gre/components/nsSessionStore.js
Line: 3844
Started "essentially" with a new Profile.
Well, actually I did start with a new Profile.
Made a few tweaks that I would typically do; load tabs on demand, remove the search bar, disable all Plugins except for Flash (set to Ask) & Adobe Reader (set to Ask) - minor stuff like that.
Closed & reopened the browser a few times.
Then...
From 2.40 copied /bookmarkbackups/, userChrome.css, userContent.css, & places.sqlite.
Closed & reopened the browser a few times.
Then I added NoScript, 2.9.5.2.
Closed & reopened the browser a few times.
Then... (the killer), sessionstore.json (2,605,460).
Started, loading from Session Store.
Seemed to do that fine.
Memory, while probably a bit higher then 2.40, within reason of what I would expect its "growth" to be. Seemed fine. Then I started opening a few sites, & within a short period of time, I'm hitting LONG delays with most every action.
Add uBlock Origin into the picture.
Restart.
Same.
Revert back to NoScript 2.0.14.
Restart.
Same.
And at the end (having now closed that Profile, & opened a different one), I was running into "black" too - parts of the browser (status bar) were black, part of the location bar, some other places too, were just, black.
I don't think its a graphics issue.
(You simply don't get much better then NVIDIA GeForce4 MX 440 .)
Oink, oink?
Thinking about the only way out of this is to ditch my sessionstore.json, which (while probably not a bad thing) would suck.
(And then after doing that, I'd have to see just what else I run into...)
(Sucks that so much is intertwined [places.sqlite] or in a not readily "readable" format [sessionstore.json, much less those .lz4 files], that one cannot [rather easily] "clean up" or pick & choose [as in to pick more meaningful data, leaving out the cruft...]...)