Firefox using all CPU in 13.2

English Install/Boot/Login
1

Now I don’t know whether this has anything to do with the upgrade to 13.2 (32bit-KDE) but on both of my laptops (Toshiba and Emachines) everything seems to be frozen every now and then. The computer does not react on mouse clicks any more and I cannot switch windows with ctrl tab. When I switch to system monitor (ctrl esc) I can see that firefox uses up to 91% of the CPU. I have to wait until the CPU usage goes down before I can continue. Now, I don’t know whether this has to do with the upgrade, with firefox or a combination of both but it definitely happened only after the upgrade on both machines. I compared this with Chromium which seems to run much faster. Has anyone else noticed something similar?
Cheers
Uli

2

I have not noticed a problem. However, I use both “noscript” and “flashblock” extensions. Those restrict what scripts and videos web sites can run on my system.

3

I use them as well together with https everywhere, better privacy, etc. Because of these extensions I would like to stay with firefox but that seems to be hopeless.

4

I also use Ghostery, and SettingSanity, which re-adds the options to disable Images, JavaScript, and the Tab Bar in the Options window.

5

I use Ghostery too and EFF’s Privacy Badger. But still no idea why suddenly the whole computer freezes and the system monitor shows high CPU usage for firefox. Cheers Uli

6

Are you using Firefox from the Mozilla repository (http://download.opensuse.org/repositories/mozilla/openSUSE_13.2/)? If not, it might be worth a try.
I’ve had no problems with that version with 13.2 32-bit KDE on a IBM ThinkPad X41.
Regards,
Howard

7

Thanks, Howard, I added this repo and switched Mozilla. Will come back later when I know more. Cheers Uli

8

You might want to disable some of the addons/extensions Sometimes those can cause problems

9

Thanks, gogalthorp, I thought about this too but they were all working fine in the 13.1 version and I had always all the updates so I think they are all the same version than in 13.1. Nevertheless I intended to try this on one computer - probalbly on the weekend. However switching to the repo howard supplied seems (so far) to have solved the problem and I am going to switch to this repo on the other computer later today. Hopefully that solves my problem. If not you will hear back from me. CHeers Uli