mozilla

Revision 474139 of How to Report a Hung Firefox

  • Revision slug: How_to_Report_a_Hung_Firefox
  • Revision title: How to Report a Hung Firefox
  • Revision id: 474139
  • Created:
  • Creator: BenjaminSmedberg
  • Is current revision? No
  • Comment Writing a doc for people who want to help a little bit with hangs.

Revision Content

Is your Firefox not responding? Or are you regularly seeing the "Firefox is running but is not responding..." dialog? This usually means that something in Firefox is hung. This may be because of a code error within Firefox itself, such as a deadlock or infinite loop, or it may be caused by 3rd-party software such as a Firefox extension, antivirus software, or even malware or a virus on your computer.

The easiest way to help the Firefox stability team to debug these kinds of hangs is to make the hung Firefox crash and submit a crash report. Then file a bug report with the crash report ID. The steps to induce a crash are slightly different on each platform:

Windows

On Windows, the stability team has written a utility which will inject a crash into Firefox which will trigger the crash reporter: Download crashfirefox.exe here (source code). Running this tool will search for firefox.exe and inject crashing code into it. The tool also has command-line options to kill processes with other names or by process ID.

  • Run this tool
  • The Firefox crash report UI should appear. Please check the box to send the crash report to Mozilla
  • Start Firefox. Type "about:crashes" in the URL bar and click on the top listing. The crash report should look something like this report, which is an example of bug 916504.
  • Create a new bug report at bugzilla.mozilla.org using this link.

Linux and Mac

On Mac, these instruction require Firefox 27 or newer. Download Firefox Nightly here.

On Linux and Mac, sending SIGABRT to a process will trigger the crash reporter. You can use any process monitoring tool to find the Firefox process ID (PID).

Finding the Firefox PID using a system monitoring tool (Linux screenshot).

Then, in a terminal, kill Firefox using a command such as this:

# Replace 31042 with the PID of Firefox found above
kill -n SIGABRT 31042
  • The Firefox crash report UI should appear. Please check the box to send the crash report to Mozilla
  • Start Firefox. Type "about:crashes" in the URL bar and click on the top listing.
  • Create a new bug report at bugzilla.mozilla.org using this link.

Other Techniques

Instead of crashing Firefox, more advanced developers who know how to use a debugger can try attaching to the Firefox process and debugging in place. This is only useful if you have Firefox debug symbols, which are available on Windows from the Mozilla symbol server.

Revision Source

<p>Is your Firefox not responding? Or are you regularly seeing the "Firefox is running but is not responding..." dialog? This usually means that something in Firefox is hung. This may be because of a code error within Firefox itself, such as a deadlock or infinite loop, or it may be caused by 3rd-party software such as a Firefox extension, antivirus software, or even malware or a virus on your computer.</p>
<p>The easiest way to help the Firefox stability team to debug these kinds of hangs is to make the hung Firefox crash and submit a crash report. Then file a bug report with the crash report ID. The steps to induce a crash are slightly different on each platform:</p>
<h3>Windows</h3>
<p>On Windows, the stability team has written a utility which will inject a crash into Firefox which will trigger the crash reporter:<a href="http://benjamin.smedbergs.us/crashfirefox.exe"> Download crashfirefox.exe here</a> (<a href="https://github.com/bsmedberg/crashfirefox-intentionally">source code</a>). Running this tool will search for firefox.exe and inject crashing code into it. The tool also has command-line options to kill processes with other names or by process ID.</p>
<ul>
  <li>Run this tool</li>
  <li>The Firefox crash report UI should appear. Please check the box to send the crash report to Mozilla</li>
  <li>Start Firefox. Type "about:crashes" in the URL bar and click on the top listing. The crash report should look something like <a href="https://crash-stats.mozilla.com/report/index/93ee95c3-9b39-419d-a6c9-909322130917">this</a> report, which is an example of <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=916504">bug 916504</a>.</li>
  <li>Create a new bug report at bugzilla.mozilla.org using <a href="https://bugzilla.mozilla.org/enter_bug.cgi?advanced=1&amp;product=Firefox&amp;Component=Untriaged&amp;cc=benjamin@smedberg.us,dmajor@mozilla.com&amp;keywords=hang&amp;short_desc=Firefox_hang&amp;comment=This_bug_was_filed_from_MDN._Firefox_is_hanging_and_manually_crashing_produces_this_crash_report:_&lt;add_link_here&gt;"> this link</a>.</li>
</ul>
<h3>Linux and Mac</h3>
<div class="note">
  <p>On Mac, these instruction require Firefox 27 or newer. <a href="http://nightly.mozilla.org/">Download Firefox Nightly here</a>.</p>
</div>
<p>On Linux and Mac, sending SIGABRT to a process will trigger the crash reporter. You can use any process monitoring tool to find the Firefox process ID (PID).</p>
<p><img alt="Finding the Firefox PID using a system monitoring tool (Linux screenshot)." src="https://mdn.mozillademos.org/files/6221/firefox-pid.png" style="width: 683px; height: 637px; margin: 4px;" /></p>
<p>Then, in a terminal, kill Firefox using a command such as this:</p>
<pre>
# Replace 31042 with the PID of Firefox found above
kill -n SIGABRT 31042</pre>
<ul>
  <li>The Firefox crash report UI should appear. Please check the box to send the crash report to Mozilla</li>
  <li>Start Firefox. Type "about:crashes" in the URL bar and click on the top listing.</li>
  <li>Create a new bug report at bugzilla.mozilla.org using <a href="https://bugzilla.mozilla.org/enter_bug.cgi?advanced=1&amp;product=Firefox&amp;Component=Untriaged&amp;cc=benjamin@smedberg.us,dmajor@mozilla.com&amp;keywords=hang&amp;short_desc=Firefox_hang&amp;comment=This_bug_was_filed_from_MDN._Firefox_is_hanging_and_manually_crashing_produces_this_crash_report:_&lt;add_link_here&gt;"> this link</a>.</li>
</ul>
<h3>Other Techniques</h3>
<p>Instead of crashing Firefox, more advanced developers who know how to use a debugger can try attaching to the Firefox process and debugging in place. This is only useful if you have Firefox debug symbols, which are available on Windows from the <a href="/en-US/docs/Using_the_Mozilla_symbol_server">Mozilla symbol server</a>.</p>
Revert to this revision