When our users crash they are pretty much in the dark about what caused the problem. They don't know about about:crashes or crash-stats.mozilla.com and probably for the most part don't care. But they do care that they are crashing. Some of them seem to be caught in an endless cycle of crashes without any idea of why. I think we can use the restore session page after a crash to better help our users by: 1. providing some indication of what caused the problem. If we can get to the data that is submitted to Socorro and analyze the top frame of the stack, we might be able to tell them that a specific plugin or addon is responsible for the crash and which page most likely caused the crash. 2. providing an easy way to disable the plugin or addon from the session restore page. Perhaps this is something that could be included in a UI sprint for 3.5.
Dave Garret's Crash reporter addon does a good job at part 1, https://addons.mozilla.org/en-US/firefox/addon/11217. Maybe something like that.
I'm checking it out right now. Thanks for the pointer! One thing though is we probably want to process the local crash data so as to not hit the Socorro servers too hard.
#2 is done via a button in the "Last Crash Information" dialog that comes up after a crash if it's an add-on's doing. This is duplicated in part with bug 336872.
This would be a big improvement. However, not having it doesn't prevent or regress major functionality in the browser, so not going to hold the release for it. If someone steps up and makes a patch that's low-footprint and well-tested, we'd take it.
blocking2.0: ? → -
should this get a "minus" for 2.0 instead of setting back to a "null state" nomination so it stays in a pool for the next release?
ah, I guess it did... more coffee...
dev-platform thread "Rethinking the crash experience": https://groups.google.com/forum/#!topic/mozilla.dev.platform/JE-E17Sp9rE Intern project "Improving Support After Firefox Crashes": https://docs.google.com/document/d/1dZkkjDh87k4UH4Gcv_gA_pkTo8yIR88l_Dxs2fXKJRs
Depends on: 1024677
You need to log in before you can comment on or make changes to this bug.