On Wed, May 25, 2016 at 3:47 PM, Eric Rahm <er...@mozilla.com> wrote: > Thanks for putting this together! > > It would be nice to see some consolidated details on how to investigate > crashes, ie loading minidumps in Visual Studio, interpreting results, > figuring out when VS is lying to you and what disassembly to look at. I > think there's some great institutional knowledge here that would be useful > to gather. Many of our developers don't use Windows regularly, so having > details on how to get going quickly would be very much appreciated.
Thank you for the suggestion. I added a dot point "Improve developer understanding of what's in a crash report", which has a couple of dot points under it. Currently the two best (and only) explanations of crash reports I know of are these: - https://air.mozilla.org/login/?next=/a-talk-about-understanding-crash-reports/, which is a talk by dbaron - https://support.mozilla.org/en-US/kb/helping-crashes > Details on using rr to debug crashes would certainly be nice. Are the docs at http://rr-project.org/ insufficient? > Additionally it would be great to see information on handling OOMs (large > and small) as those are our top crashers, and if anything I think project > uptime should be focusing on mitigating them. Fixing null derefs for a few > hundred users is nice, but fixing OOMs for tens of thousands of users is > even better! Indeed, I totally overlooked OOMs in this doc. I've added some extra information about them. Nick _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
