On Aug 10, 2010, at 12:02 PM, Jonathon Kuo wrote: > On Aug 10, 2010, at 10:55 AM, objectwerks inc wrote: >> >> On Aug 10, 2010, at 11:48 AM, Jonathon Kuo wrote: >> >>>> >>> So why does Safari blow when its VSIZE gets too large? >>> >> >> If you have too many things loaded up it is keeping part of it on disk so >> when you access things on disk continually it slows things down. >> >> But the actual VSIZE is irrelevant and does not tell you much about the >> problem except as a big picture thing. What I am trying to say is that the >> actual values and their size don't tell you that much as you have no idea >> how much if that is libraries, and how much user data. > > Agreed, but then why does the size increase monotonically?
As you add in tabs it needs more memory? Safari seems to keep each page active so the more you have, the more it needs. The VM system of the system doles out memory and so Safari gets a bunch of its memory as VM, eventually as it tries to keep the tabs active, I am guessing that it is having to constantly page stuff in and out to keep all the tabs active. > And when it reaches about 2.45GB VM, you can almost wait for Safari to blow > like clockwork. On YOUR machine. You may empirically be able to figure out about where that will happen on YOUR machine using YOUR usage patterns. I am betting that on my machine (16GB of RAM) the number is much different. I did a software update a day ago so my Safari is not up that high yet (it will be -- I typically have 1/2 dozen to dozen windows, each with a buttload of tabs -- yes I am a messy person -- just ask my wife). My point is that the number is irrelevant as a discussion point. What happens on your machine is different than my machine. And the libraries you have loaded on your machine may be different than on my machine so the amount of VM that is taken up by open libraries etc is different between machines as well. (Why is this library thing important? Each process that opens the library has the space charged against the VM even though there is only one copy of the library in memory with library code being shared across all processes that use it) >> >> What I would like to see in Safari is the ability to tell Safari to suspend >> all non screen facing tabs (either as an across the board preference or on a >> per tab basis). In other words, if a tab is not selected in a window, I >> want to be able to have Safari suspend that page until it becomes selected. >> I bet that such a feature would "solve" the problems mentioned. > > What do you mean by 'suspend'? Mark as eligible for pageout? > No, I mean suspend. Like stop processing JavaScripts, FLASH, animated GIFs, etc on the tabs that are not selected._______________________________________________ MacOSX-talk mailing list [email protected] http://www.omnigroup.com/mailman/listinfo/macosx-talk
