firefox 6
Posted: Fri 19 Aug 2011, 03:27
I noticed some weird things happening after the update to firefox 6. "pidof firefox-bin" used to be the same pid number listed in "top -n1" for firefox-bin. Now I get two numbers, the second of which matches the ppid of the firefox plugin-container in "top", but shows up for firefox-bin if I run "ps | grep ". The first number I don't see in "top" but again shows up in "ps" .
Anyway, I noticed this because my kill-clean script stopped working, because now it's necessary to kill the second number. Killing the first has no effect. I also noticed that my CPU is getting bogged down (actually, it's hard not to notice.) The plugin container alone takes 13% of resources ( oops...now it's up to 28%). I checked a few times, and suddenly firefox was taking up over 90% of the CPU. The plugin container has a wild life all it's own...god knows what it's doing. FInally, all grinds to a standstill, which only a reboot will restore. Hard to imagine what would happen if a ran a video.
I noticed a few other people are thinking along the same lines:
http://support.mozilla.com/en-US/questions/730341
I can appreciate the time and effort that has been put into making firefox progressively worse with every update, but the combined creative efforts this round have truly exceeded all expectations.
Edit: Disabled plugin through about:config. Hopefully, that should help.
Anyway, I noticed this because my kill-clean script stopped working, because now it's necessary to kill the second number. Killing the first has no effect. I also noticed that my CPU is getting bogged down (actually, it's hard not to notice.) The plugin container alone takes 13% of resources ( oops...now it's up to 28%). I checked a few times, and suddenly firefox was taking up over 90% of the CPU. The plugin container has a wild life all it's own...god knows what it's doing. FInally, all grinds to a standstill, which only a reboot will restore. Hard to imagine what would happen if a ran a video.
I noticed a few other people are thinking along the same lines:
http://support.mozilla.com/en-US/questions/730341
I can appreciate the time and effort that has been put into making firefox progressively worse with every update, but the combined creative efforts this round have truly exceeded all expectations.
Edit: Disabled plugin through about:config. Hopefully, that should help.