As a contributor or a fix it yourself type of person, reading these crash reports can be an adventure. These are the details of what each argument can mean with a lot of technical detail.
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.
Please go through each of these first to make sure the crash is actually related to Firefox.
When users submit the crash report, this is where you come to the rescue!
What to recognize in some examples:
Example reports from common crashes include Flash, hardware acceleration, out of memory crashes, plugin crashes, and add-on crashes.
Try these steps:
Follow these steps:
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.
What does each component mean?
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.
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,
The information after that will have a "+" or "-" sign describing if it's on or off.
Processor Notes: What computer saved the report.
This being concluded, you are now familiar with crash reports. Gather as much information as you can and if there is no bug filed yet, see the Contributors Guide to Writing a Good Bug.