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
No edit summary |
No edit summary |
||
| Line 5: | Line 5: | ||
* 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. | * 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. | * 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. | |||