User:KaiRo/Filing Crash Bugs: Difference between revisions

User:KaiRo/Filing Crash Bugs (view source)

969 bytes added , 5 June 2014

no edit summary

Account confirmers, Anti-spam team, canmove, Confirmed users, Bureaucrats and Sysops emeriti

4,083

edits

@@ Line 7: / Line 7: @@
 * 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.