Introduction

Have you ever submitted a crash report? No? Well, we’ll tell you what you need to know!
First take a look at Crash Stats. All of this data is part of the telemetry data that users submit when they use Firefox.

Note: If you would like to turn this on you can go to and choose from which statistics to opt into automatically.
-->Options/Preferences ---> Advanced → Data Choice

Review of the basics

Please go through each of these first to make sure the crash is actually related to Firefox.

Example 2

Challenge questions

What software is causing the problem?

Does the Modules tab show anything suspicious?

Any bugs filed?

Advanced: Filing a crash bug

Are you the first to notice more than one crash with a similar signature? Awesome, file a bug for that crash with a link to the question and add what you know from the description of the crash. To make things easier, you can submit a bug report directly from the crash-stats.mozilla.com site.

Release Channel: What channel that Mozilla product is on e.g. Beta, Nightly etc.

OS: What operating system they’re running.

Build Architecture: 32 or 64-bit processor.

App Notes: Internal Firefox Settings.

System Memory Use Percentage: How much memory that product was using.

Where to look first:

Version: The version will be on top of the crash.

Extension tab: Use this to find out what add-ons are installed.

Check the version of the operating system that the crash report was sent from with the tag in the forum.

Signature of the last frame module: The search time period is important to take note of if you notice a trend of crash reports.

Search: These are advanced reports.

UUID: The crash report id number.

Process Type: Used to figure out what caused the problem. This will include the module's file type. For example, typically it will say plugin or Firefox crash.

Build Architecture: This is the type of processor. This can be AMD, Intel, etc.

Crash reason: This is a generic error that is defined in the code of Firefox that is returned when an error occurs. For example, bad write may mean it could not write some data to the computer's memory.

Apps Notes: These are the vendor ids. This includes the make, model and version of the computer's video card. For example,

Adapter AMD: X.X.X.VERSIONNUMBER

NVIDIA: 900.XXX.XX

The information after that will have a "+" or "-" sign describing if it's on or off.

Processor Notes: What computer saved the report.

Make the support count! This is a great example where this all comes together!