User:CF:Fx2 Hangs: Difference between revisions
No edit summary |
mNo edit summary |
||
| Line 1: | Line 1: | ||
There have been several people coming into <i>#firefox</i> reporting problems with hangs since installing Firefox 2. As far as I know the usual tests of safe mode and new profiles haven't turned up anything, and the lack of Talkback data makes it pretty hard to debug. | There have been several people coming into <i>#firefox</i> reporting problems with hangs since installing Firefox 2. As far as I know the usual tests of safe mode and new profiles haven't turned up anything, and the lack of Talkback data makes it pretty hard to debug. This also seems to be a Windows problem (but that may just be that there are many more users on this OS) and there are no steps to reproduce. | ||
To try to make some progress, the intrepid Mook has adapted his crash utility to make it easier for noobies to use. The idea is that it triggers a crash, Talkback kicks in, and then there are stacks for clever people to look at. His page is [http://mook.moz.googlepages.com/ here], the util is called <tt>crash3</tt>. | To try to make some progress, the intrepid Mook has adapted his crash utility to make it easier for noobies to use. The idea is that it triggers a crash, Talkback kicks in, and then there are stacks for clever people to look at. His page is [http://mook.moz.googlepages.com/ here], the util is called <tt>crash3</tt>. | ||
Revision as of 17:27, 9 November 2006
There have been several people coming into #firefox reporting problems with hangs since installing Firefox 2. As far as I know the usual tests of safe mode and new profiles haven't turned up anything, and the lack of Talkback data makes it pretty hard to debug. This also seems to be a Windows problem (but that may just be that there are many more users on this OS) and there are no steps to reproduce.
To try to make some progress, the intrepid Mook has adapted his crash utility to make it easier for noobies to use. The idea is that it triggers a crash, Talkback kicks in, and then there are stacks for clever people to look at. His page is here, the util is called crash3.
The steps to use it are
- download the pre-built binary and save it to the harddisk (the Desktop is convenient)
- open it (double clicking will do)
- confirm that it's attempting to kill the right application (firefox.exe) and hit enter. Otherwise bail out with Control-C or by closing the DOS window
- submit the Talkback report
- open Talkback (if not the first time it has run)
- copy the ID and paste it back to you
crash3 looks for the process/thread that is consuming more than 80% CPU, so we need to first verify if the person is suffering from CPU loaded hangs, or just zero/low CPU freezes.
Feel free to add Talkback ID's, conversation summaries, speculation and so on below the line. Hopefully we can narrow it down enough to start to file a bug (or bugs).