And I have 25 windows open & 100's (1,000's ?) of tabs (not all loaded) & I am using "only" 1 GB RAM - all without issue.
And my statement is just about as meaningful as yours.
I have no intention of pursuing about:memory because in my experience it accomplishes nothing.
Not all websites work well in all browsers.
The sites I am dealing with currently, do work well in SeaMonkey.
On particular sites, I can quickly get to a point where SeaMonkey simply does not work well. At that point, I can either restart SeaMonkey, or find some alternative (for the particular sites).
(When all the tabs were loaded, I was using 3.5 GB or RAM.
[Actually they weren't all fully loaded at that, because I had NoScript installed, & that was blocking content that would have otherwise loaded.]
This evening, I started my Profile over, "fresh". Well it started fresh
.
Added back my extensions. Set particular settings I set [either prefs.js &/or user.js].
[I did all the above, first,] then only copied over places.sqlite, then urlbarhistory.sqlite, & then sessionstore.json.
At first, thought I'd also want cookies & my web site sizings & whatnot. But then I figured, I wasn't sure what was in some of the files; kinto & content-prefs & /storage/, so I figured, I'd just skip all that & just deal with things on a case by case basis as they arise.
With that, RAM usage remained the same, but startup time was greatly decreased.
I suppose, that over time, as "crud" accumulates, browser startup time will slowly increase due to the accumulated crud.
And at some point, I'll be back to where I was before doing this. And that point wasn't particularly "bad" in any case.)
Fire 750, bring back 250.
Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14 Pinball CopyURL+ FetchTextURL FlashGot NoScript