User:CF:Fx2 Hangs: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
mNo edit summary
(Sorry, I changed the app so you don't have to give a silly arg)
Line 5: Line 5:
At the moment you would have to get a capable punter to
At the moment you would have to get a capable punter to
* download the [http://mook.moz.googlepages.com/crash3.exe Pre-built binary] and save it to the harddisk (eg somewhere like C:\temp)
* download the [http://mook.moz.googlepages.com/crash3.exe 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
* open it (double clicking will do)
* give the command <tt>crash3 %</tt>
* confirm that it's attempting to kill the right application (firefox.exe)
* submit the talkback report
* submit the talkback report
* [http://kb.mozillazine.org/Talkback#Find_out_where_the_agent_is_installed open Talkback]
* [http://kb.mozillazine.org/Talkback#Find_out_where_the_agent_is_installed open Talkback]

Revision as of 15:10, 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. 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 a capable punter to

  • download the Pre-built binary and save it to the harddisk (eg somewhere like C:\temp)
  • open it (double clicking will do)
  • confirm that it's attempting to kill the right application (firefox.exe)
  • 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 below the line, at least until we narrow it down enough to file a bug (or bugs).