Firefox 4 plugin_container.exe uses 75% of CPU with Add-ons disabled
I looked at support entries for plugin_container but they seem to be 9 months old. Mine is a problem with FF4.0, downloaded shortly after it became available. I have restarted FF4 in safe mode, with Add-ons disabled, following advice I saw re FF3.6. But the behaviour is the same: plugin_container.exe takes 116 to 140 Mb of memory and sits at the top of my CPU usage. On the Yahoo (UK) homepage I have seen it take 63 to 81% - doing what exactly?? When running BBC iPlayer it takes only about 40% of CPU. When on a different page (but with Yahoo in a tab) usage is around 20%. When Yahoo is closed it goes down to 0%. So what is special about Yahoo??
由 hmbhmb 於 修改
所有回覆 (4)
Augmented the above with screenshot showing CPU usage on Yahoo home page.
Had the exact same problem, so I disabled each plugin one by one and as soon as I got to Shockwave Flash (latest version!) CPU-usage went down to 1-2%. Downloading the latest version again and installing it manually after closing FF4.0 helped to fix the issue!
Update an hour later: Sorry, didn't help at all, it's up at 55% again. Stuck with a spinning fan just like at the beginning...
由 cee_ess 於 修改
after some research, here's what i found. seems like flash player has some issues when running out-of-process, here's how flash can be prevented from doing so: http://kb.mozillazine.org/Plugin-container_and_out-of-process_plugins#Firefox_4
also, here i read, there seems to be an issue with flash using hardware acceleration: http://support.mozilla.com/en-US/questions/796191
for me, right-click settings on a paused TED-video, disabling hardware acceleration helped already a lot! :)
cee-ess, you're right that it seems to be an issue with Flash movies. Yahoo sometimes runs these on its homepage (as adverts, i think).
I could not understand the notes in your first link, but thanks anyway.
I switched off hardware acceleration as you suggested, but the playing the movie still causes plugin_container to use 90% of CPU. It's the same with YouTube.
This seems to be a bug either with Flash (version 10,2,153,1 ) or firefox v4 or the combination. I don't think I had this problem with earlier versions.