On 11/28/2010 3:37 PM, Phillip Jones wrote:
Justin Wood (Callek) wrote:
On 11/27/2010 8:52 PM, Phillip Jones wrote:
Ant wrote:
I just accidently pressed ctrl-T and got a tab in it. Am I the last
user
to know this? Did SM1 and Mozilla have this too? :(
No SM couldn't thank goodness.
I don't even use tabs in browser for SeaMonkey or in FF. The only thing
its good for is wasting memory as each tabbed item takes up memory.
MUCH Less memory than a new window though, fwiw.
But your only viewing each window one at a time. and it replaces in
memory the previous window's contents.
However in a new window, you are creating an entire new HWND in windows
(or similar in other OS's) [slightly changed in trunk] which only has
one active state per |window| context, which in a global window has at
minimum two window contexts, (one for the chrome, one for the content).
So when you create a new window, you get 2 more contexts. With a new
tab, just one more.
And you still only peg the Paint Paths for one tab at a time, rather
than having the Frame Tree/View Manager coalesce paths for multiple
windows with multiple contexts.
Its like a slide show. you
completely replace the content in one window with the content in another
window. In tabs your saving the content as a separate instance. when you
have more than two tabs in memory that's a big drain on the RAM.
The drain on RAM is per-process. If we had separate process WINDOWS (not
tabs) this might make more sense. In reality all windows, as well as all
tabs, are primarily in one thread [for now]. except network requests and
some other nuances [which are irrelevant here]. So you are not saving
anything by added windows.
Then
the hard drive comes into play and drags everything down waiting for the
swaps. (unless you have one of those solid state devices). Even that
drags the SSD down eventually causing its demise at shorter interval.
This is [almost] your only realistically relevant point. The fact that
if you have a small amount of RAM and you start paging into your HD for
memory. Then by not accessing other windows, you don't see as much of a
drain because the memory associated with those other windows is
infrequently needed. [window contexts mostly, of course frame trees etc
too]. Whereas tabs are relatively small comparatively, so when you need
to page stuff in you might -think- you are using more memory, though the
facts of the matter don't show that faithfully.
I had simply replied to the earlier post to illustrate for the reader of
your post that new tabs vs new windows are much better for RAM use, and
not to denigrate your personal preference, which I can respect and do
not fault you for. But I felt I needed to correct many of these
inaccuracies in your last message here. I don't feel that illustrating
further will be necessary, even if you provide further fallacy's to this
thread.
--
~Justin Wood (Callek)
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
