Firefox gets stuck and keeps one core fully loaded

Ripper-tm · n00b Joined: 29 May 2011 Posts: 13

Under unknown circumstances firefox begins to eat 100% on [sometimes more than] one core. If all FF windows closed, the process will remain and will still be doing its unknown stuff, heavily loading one cpu. After that it will be impossible to start a new window as it will tell you "FF is already running". killall (with standard signal) helps.

Since it happens very frequently but always unexpectedly, I'm looking for an any way to constantly debug FFs behavior.
_________________
Ripper-tm's English language support is a work in progress

eccerr0r · Posted: Thu Aug 22, 2013 5:27 pm Post subject:

Which architecture? Any specific web page? Is it a plugin issue?

I had firefox hang randomly on ia64, and I heard it was rootcaused to a rampant garbage collecting routine. Because ia64 isn't "supported" they wouldn't take the patch. I wonder if the same bug affects other non x86/x86_64 architectures...
_________________
Intel Core i7 2700K/Radeon R7 250/24GB DDR3/256GB SSD
What am I supposed watching?

Ripper-tm · n00b Joined: 29 May 2011 Posts: 13

amd64. I haven't yet found out if it is caused by a specific page *. And, the only plugin I'm using is AdBlock.

* The problem is that the only way to detect the appearance of this bug is to constantly monitor resouces. FF doesn't hang in a general sense, it starts an unknown heavy singlethreaded workload that does not noticably affect performace on a multicore system.
_________________
Ripper-tm's English language support is a work in progress