Setting "--memory-model=high" seems to have done it. Performance of Chrome 0.2.153.1-build 2519 (updating on the "Dev" channel) is vastly improved by what I've seen so far, especially for any tab showing Flash based media where reclaiming memory after the tab was closed would drive my single core CPU through the roof. Also, the Flash plugin is no longer crashing on a regular basis when attempting to manipulate a Flash based video in any way, shape or form (like Stop, Pause, fwd, back, etc).
Now, I don't suppose anyone could point me to an explanation of what this particular command line flag does exactly? I've looked at http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/chrome_switches.cc?view=markup and although it does list the command line switches (ie: "memory-model"), it doesn't explain the settings (ie: "=high") that can be used for each individual switch switch (Boolean, integer, string value, high, low, medium...what?) or what the settings for each switch accomplishes. Is there any documentation that explains this (akin to: Mozillazine's Knowledge Base for Firefox's configuration settings ["about:config"]) or is something like that not yet available? On 9/30/2008 4:56 PM, Dean McNamee wrote: > Does running with the --memory-model=high command line flag help the > situation? > > On Tue, Sep 30, 2008 at 10:28 PM, Charles Allen > <[EMAIL PROTECTED]> wrote: > >> Same thing here. I saw elsewhere that if you disable the fishing/ >> malware options it lowers this effect, but I haven't been browsing >> enough to know for sure if it works. >> >> On Sep 21, 3:26 pm, Kirk M<[EMAIL PROTECTED]> wrote: >> >>> I'm finding when Chrome (beta versions *.27, *.29, *.30) and Chrome >>> "Dev" version 0.2.152.1 drives a single core CPU close to 100% >>> apparently while reclaiming memory from a closed tab especially when the >>> page within the tab contained a site that was Flash heavy. This in turn >>> makes the browser (and the OS) completely unresponsive for seconds at a >>> time. Any particular reason this might happen? >>> >>> System stuff: >>> >>> Microsoft Windows XP Professional >>> Version 5.1.2600 Service Pack 3 Build 2600 >>> System Type: X86-based PC >>> Processor: x86 Family 6 Model 10 Stepping 0 AuthenticAMD ~2200 Mhz (P4 >>> 3.0 Ghz equiv.) >>> Total Physical Memory: 1,024.00 MB >>> >>> Google Chrome: 0.2.152.1 (Official Build 2164) >>> WebKit: 525.19 >>> V8 0.3.0 >>> User Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US) >>> AppleWebKit/525.19 (KHTML, like Gecko) Chrome/0.2.152.1 Safari/525.19 >>> >>> > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/chromium-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
