User:CF:Fx2 Hangs: Difference between revisions
(1st cut) |
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 anything, and the lack of Talkback data makes it pretty hard to debug. As far as I know this is a Windows problem, but that may just be that there are many more users on this OS, and here are no steps to reproduce. | 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 anything, and the lack of Talkback data makes it pretty hard to debug. As far as I know this is a Windows problem, but that may just be that there are many more users on this OS, and here are no steps to reproduce. | ||
To try to make some progress, the entrepid 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 crash3. | To try to make some progress, the entrepid 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>. | ||
At the moment you would have to get the punter to | At the moment you would have to get the punter to | ||
Revision as of 14:23, 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 anything, and the lack of Talkback data makes it pretty hard to debug. As far as I know this is a Windows problem, but that may just be that there are many more users on this OS, and here are no steps to reproduce.
To try to make some progress, the entrepid 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.
At the moment you would have to get the punter to
- download the Pre-built binary and save it to the harddisk (eg somewhere like C:\temp)
- open a command window and cd into the dir where it is saved
- give the command crash3 %
- submit the talkback report
- open Talkback
- copy the ID and paste it back to you
crash3 looks for the process/thread that is consuming CPU and kills that, so we need to first check if these are CPU loaded hangs or zero/low CPU freezes.
Feel free to add Talkback ID's, summaries, speculation and so on here, at least until we narrow it down enough to file a bug (or bugs).