On Thu, Oct 15, 2009 at 11:11 AM, Jens Alfke s...@google.com wrote:
• Switching to another tab in the same window is the only way to get
heap usage down significantly (by calling V8's IdleNotification) and
even then it takes over a minute of occasional idle-time GC to have a
significant
On Thu, Oct 15, 2009 at 11:11 AM, Jens Alfke s...@google.com wrote:
I spent some time this morning looking at Chrome's memory usage (on OS
X 10.5.8) while viewing flickr.com. First I simply started at my photo-
stream page and hit Reload over and over. Next I tried going through
all of my
On Thu, Oct 15, 2009 at 11:11 AM, Jens Alfke s...@google.com wrote:
I spent some time this morning looking at Chrome's memory usage (on OS
X 10.5.8) while viewing flickr.com. First I simply started at my photo-
stream page and hit Reload over and over. Next I tried going through
all of my
On Thu, Oct 15, 2009 at 11:57 AM, Mike Belshe mbel...@google.com wrote:
• We should call V8::IdleNotification in situations other than a
hidden tab. A long-lived tab might go for quite a while without being
hidden in this way: the user might activate another app, hide Chrome
itself, or just
