Hi Nick, Wasn't sure how you wanted feedback. Here's some in email form.
"Crashes are caused by defects" Reading this I think it implies defects in Firefox. This is not always the case. Crashes are also the result of interactions with third party software. Both that that we designed for (like NPAPI plug-ins) and that we didn't (AV, malware), which you mention lower down in the doc. "Improve ranking of crash clusters." I think this is weighting or estimating impact of a crash instead of volume of submissions, which is how we have historically processed the clusters. Severity is one component with startup crashes being worse than content crashes being worse than shutdown crashes. (Need to figure out weighting of gfx and other buckets of crashes.) Potential impacted population is another and we have data on the differences in population size on Beta vs Release for dimensions like OS version, gfx hardware, and gfx driver to make use of for the weighting. "Improve reproducibility of these crashes. - Use rr to record crashes so they can be played back reliably." We're going to spin up a project to work on debugging in automation. We've talked about having the ability to run a test until it fails and pause at that point. I think that would be very helpful for this case. I didn't see a lot on mitigation strategies but I think those this is key piece as well. We will get some mitigation when e10s ships and content crashes no longer take down the whole browser. We've discussed mitigations for startup crashes (and implemented one for gfx). What other mitigations should we put in place to recover gracefully? Thanks for putting this together! Lawrence On Tue, May 24, 2016 at 12:56 AM, Nicholas Nethercote < n.netherc...@gmail.com> wrote: > Greetings, > > I've written a document called "All about crashes" which I've put on > the Project Uptime wiki: > > https://wiki.mozilla.org/Platform/Uptime#All_about_crashes > > It's about all the different ways we can discover, diagnose, and > address crashes. It's intended to be a comprehensive, because I want > to use it to help identify and prioritise all the ways we could do > better. > > I would appreciate any feedback people might have. I'm sure I have > gotten some things wrong, and omitted some things. Thanks in advance. > > Nick > _______________________________________________ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
