When [[Firefox crashes]] and a user asks for help, viewing the crash report will help you to better understand the cause of the crash (e.g. extensions, third party software) and provides useful information needed to find a solution, such as related bug reports. This article describes that troubleshooting process. __TOC__ = Viewing crash reports = To view your crash reports from within Firefox: # In the Location bar, type '''about:crashes''' and press {for win,linux}{key Enter}{/for}{for mac}{key Return}{/for}. A list of links to submitted crash reports will appear.<br><br>[[Image:Helping Crashes 1]]<br> <br> # Click on a link to view the report. == Viewing crash reports outside of Firefox == If you can't use the above method because Firefox crashes when it starts, even in [[Safe Mode]], you can also view crash reports by locating the text file stored on your computer that corresponds to the submitted crash report: {for win} # Press {key _{[[Image:Windows Key]]}+R} (click the Windows {button Start} button and select {menu Run...} on Windows XP). # In the Run dialog box, type {filepath %APPDATA%\Mozilla\Firefox\Crash Reports\} and press {key Enter}. {/for} {for mac} Crash reports are stored in {filepath ~/Library/Application Support/Firefox/Crash Reports/} {/for} {for linux} Crash reports are stored in {filepath ~/.mozilla/firefox/Crash Reports/} {/for} The {filepath Crash Reports} folder will contain two subfolders: {filepath pending} and {filepath submitted}. Each file in the {filepath submitted} folder represents a submitted crash report and its name contains the Crash ID. To view the crash report, you would enter the following URL in the Location bar:<br>'''https://crash-stats.mozilla<!---->.com/report/index/''CrashID''''' For example, to view the crash report for the Crash ID ''bp-2de07d12-0cde-45b2-a555-2d2d72111011'' you would enter the following in the Location bar: <br> '''https://crash-stats.mozilla<!---->.com/report/index/bp-2de07d12-0cde-45b2-a555-2d2d72111011 = Figuring out a crash report = [[Image:Helping Crashes 2]] A crash report contains many useful pieces of information: * ''ID'' - Allows you to view a crash report by typing '''https://crash-stats.mozilla<!---->.com/report/index/bp-''CrashID''''' in the Location bar. * ''Signature'' - Describes the kind of crash. You can view every crash report with the same crash signature over one week across all Firefox versions by typing '''https://crash-stats.mozilla<!---->.com/report/list?signature=''CrashSignature''''' in the location bar. * ''Details'' pane: ** ''Header'' - Contains details about the crash time, crash reason, Firefox version, OS, CPU, graphics settings, and the [http://en.wikipedia.org/wiki/Layered_Service_Provider LSP]. ** ''Related Bugs'' - Bugs related to this crash signature. A bug can have different status: UNCONFIRMED, NEW, ASSIGNED, REOPENED, RESOLVED, VERIFIED, CLOSED. If its status is FIXED, the Target Milestone and Tracking Flags fields will tell you from which version it has been fixed. Check all comments to see if there's a known workaround. ** ''Crashing Thread'' - Shows the last function calls before the crash. You can see if third party software is implied. The bug component is usually the component which the last called functions belongs to. * ''Modules'' pane - The loaded processes when it crashed. Filenames without version on Windows are often malware and may be the cause of the crash. *''Raw Dump'' pane - Crashing thread before it's post-processed in an interpretable way. *''Extensions'' pane - User's extensions. Known buggy extensions must be checked here. *''Comments'' pane - User's comment written when Mozilla Crash Reporter was opened and may help to understand how it takes place. *''Correlations'' pane - Tables of correlation data (modules, add-ons, CPU cores) for this crash signature and reason elaborated from all the crashes of the day in the current Firefox version. The higher the ratio is between the two percentages, the higher the correlation is. Correlations per module and per add-on must be checked to see if it's caused by third party software or add-ons.

When Troubleshoot Firefox crashes (closing or quitting unexpectedly) and a user asks for help, viewing the crash report will help you to better understand the cause of the crash (e.g. extensions, third party software) and provides useful information needed to find a solution, such as related bug reports. This article describes that troubleshooting process.

Viewing crash reports

To view your crash reports from within Firefox:

1. In the Location bar, type about:crashes and press EnterReturn. A list of links to submitted crash reports will appear.
   
   
   
   
2. Click on a link to view the report.

Viewing crash reports outside of Firefox

If you can't use the above method because Firefox crashes when it starts, even in Use Troubleshoot Mode in Firefox, you can also view crash reports by locating the text file stored on your computer that corresponds to the submitted crash report:

The Crash Reports folder will contain two subfolders: pending and submitted. Each file in the submitted folder represents a submitted crash report and its name contains the Crash ID. To view the crash report, you would enter the following URL in the Location bar:
https://crash-stats.mozilla.com/report/index/CrashID

For example, to view the crash report for the Crash ID bp-2de07d12-0cde-45b2-a555-2d2d72111011 you would enter the following in the Location bar:
https://crash-stats.mozilla.com/report/index/bp-2de07d12-0cde-45b2-a555-2d2d72111011

Figuring out a crash report

A crash report contains many useful pieces of information:

• ID - Allows you to view a crash report by typing https://crash-stats.mozilla.com/report/index/bp-CrashID in the Location bar.
• Signature - Describes the kind of crash. You can view every crash report with the same crash signature over one week across all Firefox versions by typing https://crash-stats.mozilla.com/report/list?signature=CrashSignature in the location bar.
• Details pane:
  • Header - Contains details about the crash time, crash reason, Firefox version, OS, CPU, graphics settings, and the LSP.
  • Related Bugs - Bugs related to this crash signature. A bug can have different status: UNCONFIRMED, NEW, ASSIGNED, REOPENED, RESOLVED, VERIFIED, CLOSED. If its status is FIXED, the Target Milestone and Tracking Flags fields will tell you from which version it has been fixed. Check all comments to see if there's a known workaround.
  • Crashing Thread - Shows the last function calls before the crash. You can see if third party software is implied. The bug component is usually the component which the last called functions belongs to.
• Modules pane - The loaded processes when it crashed. Filenames without version on Windows are often malware and may be the cause of the crash.
• Raw Dump pane - Crashing thread before it's post-processed in an interpretable way.
• Extensions pane - User's extensions. Known buggy extensions must be checked here.
• Comments pane - User's comment written when Mozilla Crash Reporter was opened and may help to understand how it takes place.
• Correlations pane - Tables of correlation data (modules, add-ons, CPU cores) for this crash signature and reason elaborated from all the crashes of the day in the current Firefox version. The higher the ratio is between the two percentages, the higher the correlation is. Correlations per module and per add-on must be checked to see if it's caused by third party software or add-ons.