Community:SummerOfCode19:Brainstorming: Difference between revisions

Community:SummerOfCode19:Brainstorming (view source)

1,095 bytes added , 21 January 2019

Added the 'Helpful crash reporter' entry

Confirmed users

407

edits

@@ Line 113: / Line 113: @@
 | [https://mozillians.org/en-US/u/odvarko/ Jan Odvarko]
 | [https://docs.google.com/document/d/153Yaxs3vG0rreYXgYzGuROaeiU0buKvDM3YznTOQtR4/edit Product Requirement Specification]
+|-
+| Helpful crash reporter
+| The crash reporter only allows users to send crash reports but in some cases it might help the user diagnose the crash and solve it on his/her own
+| C++, Javascript
+| [https://mozillians.org/en-US/u/gsvelto/ Gabriele Svelto]
+| [https://mozillians.org/en-US/u/gsvelto/ Gabriele Svelto]
+| There's a few things that could be implemented:
+* A quick test of the memory owned by the crashed process (such as those in [http://www.memtest.org/ memtest86+]) might catch faulty memory, a common cause for crashes
+* The crash reporter client might try and validate Firefox files which can sometimes become corrupted (usually because of hardware issues). If they are it can prompt the user to re-install Firefox
+* Many crashes are caused by buggy graphics drivers, while we blacklist the most egregious offenders we can't cover them all. The crash reporter might identify a faulty driver (if a bug for it has already been filed) and point the user to up-to-date drivers
+* For crashes caused by known bugs it should be possible to point the user to the bug filed on bugzilla
 |-