I noticed a few months back (and consistently thereafter) that the performance of these flash applications was unruly — as in they would slow to a crawl, animations would studder, sometimes the browser would just lock up and become unusable. Really annoying to have Firefox lock up like that. To have it become frozen and lose twelve tabs worth of half-read web pages?
Usually they would recover but the waiting is a pain.
In the task manager was an entry for “plugin-container.exe” — where I’m assuming Firefox dumps flash application data and cache while it is processing the flash app. The memory load for firefox.exe would be 300-500 meg while the plugin-container was around 20-35 meg. A case of inefficient memory swapping? Possibly.
I can’t say if that plugin container or the memory management in firefox is specifically to blame. It could be that the Firefox crew didn’t reserve enough room for the more robust uses of flash these days, or it could be more of a matter of the number of plugins I have installed in Firefox in order to assist with web development. JQuery or heavily use of Javascript like Google Docs and facebook might not have helped either.
In any case, the sure fire workaround was to let Google Chrome have a shot at the workload.
It’s been working like a charm. No browser hang-ups. Chrome is not only fast as they say, but it is handling the flash apps like a hero.
But lose firebug and all those handy apps? No way. Firefox is still open in my system tray, and ready to help me with all those awesome plugins.
Related Articles
3 users responded in this post
Nice site .
Way back on FF 3.6.4, mozilla introduced the plugin-container to manage out of process plugins, such as Flash.
Apparently there’s some bug there, as it often hangs the system using around 100% of the CPU (25% in a quad-core system, etc.), and lots of memory. Upgrading to FF4 and FF5 didn’t help this one bit.
Fortunately, there’s a quick workaround, though:
1) open FF, and in the URL address bar write:
about:config (then press return, as if this was a URL)
2) dismiss the warning message and continue.
3) filter for dom.ipc.plugins and set all the “enabled” variables to FALSE. This will prevent handling OOPPs through plugin-container
4) restart FF. You should be good now.
Cheers.
@the guitar man
Thanks! I wonder how much of the market share firefox lost to chrome due to not working out that bug. Too bad really, because the extensions for FF are so handy.
Leave A Reply