Red Hat Bugzilla – Bug 474568
freeze for approximately 30 seconds
Last modified: 2009-11-18 07:04:17 EST
Created attachment 325677 [details]
backtrace of freezing firefox
Description of problem:
Firefox is sometimes freezing for longer time period. It's happening since firefox3 with or without flash application.
Version-Release number of selected component (if applicable):
I'm not sure how could it be reproduced. Maybe the backtrace will help. After running dbg it froze immediately.
How it looks:
It could happen when I'm editing bugzilla or when I'm switching from one desktop to another.
Hm, it seems to hang somewhere in nss/nspr, if the backtrace is relevant...
Kai, any thoughts on this?
It is no excuse for us, just to note that Marcela's primary desktop is KDE.
Where do you see a hang in nspr/nss? I don't see anything unusual.
Most threads wait for something to happen (waiting for pthread condition variables).
Some other threads are polling, but that doesn't seem unusual to me.
Can you try to run with your extensions disabled?
The next time you run into the freeze...
- does your cpu usage go up to 100% ?
- using gdb, can you repeatedly use continue and break again, and compare the threads, in order to identity a potentially looping thread?
Ok, I disabled all extension.
The cpu doesn't take more than usual because everything else is going just fine. I'll be waiting for another freeze.
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '10'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 10's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 10 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
This was already fixed in F-11.