Account confirmers, Anti-spam team, canmove, Confirmed users, Bureaucrats and Sysops emeriti
4,083
edits
User:KaiRo/Filing Crash Bugs: Difference between revisions
no edit summary
(Created page with "This is a '''DRAFT''' for an article that might go up on MozillaWiki or MDC, wherever it fits better. If you file a bug for a crash you have encountered or found via [https:/...") |
No edit summary |
||
| Line 2: | Line 2: | ||
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. | 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. | |||