User:KaiRo/Filing Crash Bugs: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
(Replaced content with "This document has been moved to [https://developer.mozilla.org/en-US/docs/Mozilla/QA/Filing_Crash_Bugs MDN: Mozilla/QA/Filing_Crash_Bugs].")
 
(6 intermediate revisions by 2 users not shown)
Line 1: Line 1:
This is a '''DRAFT''' for an article that might go up on MozillaWiki or MDC, wherever it fits better.
This document has been moved to [https://developer.mozilla.org/en-US/docs/Mozilla/QA/Filing_Crash_Bugs MDN: Mozilla/QA/Filing_Crash_Bugs].
 
If you file a bug for a crash you have encountered or found via [https://crash-stats.mozilla.com/ crash stats], there are a few rules you can follow if you want developers to be as efficient as possible in actually debugging the problem and finding a fix.
 
* For one thing, use the "Bugzilla - Report this bug in ..." links in a representative crash report on crash-stats (under the table of crash information on the "Details" tab). If you are looking at a list of crashes, e.g. a Signature Summary, you ideally look through a few reports to select a representative that has a good stack and as few extensions installed as possible.
* Select a fitting product and component for what you think is the cause of the crash. In doubt, take an as educated as possible guess. Nobody will think less of you when you guess wrong - but if you guess at least somewhat right, chances for seeing the bug resolved are higher.
* Make sure a link to the representative crash is in the initial comment, the Crash Signature field filled out and the "crash" keyword set on the bug. If you used the "Report this bug" links, then this is already done correctly.
* Include a link to more reports with the same signature, e.g. by copying the URL from the "More Reports" link next to the signature in the Details table of the crash report.
* It helps including the top few stack frames in the bug - you can potentially cut the list off at a point where it seems to go generic and unrelated to the actual issue, but if you are not sure, include it all.
* If it's a crash you encountered, it helps to tell developers in the bug what you remember doing when the crash occurred, if possible.
* If you file based on data, please include data about when it started to appear, how high it is in overall volume (and/or topcrash reports), and any information that is outside the average sample (i.e. only happening on specific OSes, specific Firefox versions, specific Graphics cards, or significant correlations with any modules or add-ons). Also, if comments tell anything about commonalities of actions and/or possible steps to reproduce, please include that.
* Include any clues you have about this crash could be reproduced. When a developer can reproduce the crash, it's very likely they can find a fix as well.

Latest revision as of 22:17, 12 February 2015

This document has been moved to MDN: Mozilla/QA/Filing_Crash_Bugs.

Retrieved from "https://wiki.allizom.org/index.php?title=User:KaiRo/Filing_Crash_Bugs&oldid=1055854"