On a planet called Veridian III, a decisive battle was fought to prevent a future firing of a rocket into a star that would change gravitational forces and make "the nexus" crash into the planet as well as destroy the planet with a shock wave. Preventing this catastrophy made the crash of the USS Enterprise on the planet controllable as to suffer no human casualties.
In the same spirit, the project I internally dub "Veridian 3" is about dealing with crashes to make the bad ones preventable and other ones more controllable, all through prioritizing Socorro work.
Those areas have been specified in the contract:
- Improving Crash Data Integrity
- Identification and Removal of Duplicate Crash reports
- Improving Search Capabilities
- Improving Classification and Characterization of Crash Reports and Improved Signature Generation
- additional correlation reports to help identifying circumstances around the crash and steps to reproduce
- Improve Trend Reports to identify and alert teams about Explosive bugs
Prioritization Comments From Socorro Users
<wsmwk> KaiRo: second tier needs might be bug 421119, bug 518823, bug 578376, bug 411354. third tier: bug 527304, bug 512910, better workflow for updating skiplist) <firebot> Bug https://bugzilla.mozilla.org/show_bug.cgi?id=421119 min, P3, 2.1, nobody, NEW, function for socorro to compare stacks of two or more crash reports <firebot> Bug https://bugzilla.mozilla.org/show_bug.cgi?id=518823 enh, --, Future, nobody, NEW, indicate bug's status for bugzilla keyword topcrash <firebot> Bug https://bugzilla.mozilla.org/show_bug.cgi?id=578376 nor, --, ---, nobody, NEW, multiple crashes from a single person should have less weight then many crashes from different peopl <firebot> Bug https://bugzilla.mozilla.org/show_bug.cgi?id=411354 nor, P1, 2.0, nobody, REOP, Add ability to search by build ID <firebot> Bug https://bugzilla.mozilla.org/show_bug.cgi?id=527304 enh, --, ---, nobody, REOP, provide smart analysis ala talkback <firebot> Bug https://bugzilla.mozilla.org/show_bug.cgi?id=512910 enh, --, ---, nobody, NEW, Make it easier to analyze crashes that share a signature
https://bugzilla.mozilla.org/show_bug.cgi?id=551669 provide graphs by crash date too Smokey Ardisson (way behind; no bugmail - do not email) <email@example.com> changed: CC| |firstname.lastname@example.org
johnjbarton Of course *all* of my crashes involve Firebug. The number one question I have when I visit crash-stats site is: How many other users who have this crash also running Firebug? If the answer is 95%, then I better spend some time on it because no one else will. If the answer is 5%, I'm having lunch. Regarding the point about "correlations" page, I've never found that info to be useful, sorry. I have looked at it, but I don't recall every finding something useful.
Jeff Muizelaar It would be nice if it was possible to get more summary information about a crash. For example: What build ids does this crash all occur with? What operating system versions does this all occur with? etc.
Josh Matthews I, like Jeff, would appreciate summaries of the data available - most recent 10 unique build ids, list of unique OS versions, range of uptimes, etc. I would also be really interested in data about spikes - seeing a graph of the number of crashes for a particular signature over time would be useful to track trends.
Honza Bambas - definitely voting for search also by other frames then just the top frame (the signature) ; regular expressions would also be useful, but not necessary (for me) --> Template:Bug - when searching for regression ranges I sort the results by buildID, if there are several result pages, then going to another page forgets the sort-by option => would be great to show only the buildIDs the crash matching the query occurs in ; to include also the branch (e.g. tracemonkey) in the list would be helpful - direct access to the repository revision would be also helpful, but it is more about just changing the web UI, the information is already there, just makes more work to access - a link to the nightly build directory on the ftp server would also be good, but for me not necessary (I can always build from the given rev my self) ; If needed I look for a nightly by the .txt file that cointains the buildID, really not convenient
dmandelin - When did this crash start happening, or start happening often? The graph view we have is very helpful, but it only shows 4 weeks at a time, which is not always enough. Template:Bug (Template:Bug, Template:Bug) - Search for crashes by crash address. Sometimes we add diagnostics that will make Firefox crash at certain addresses. We can't currently search for this directly in Socorro. There's a bug on file for this. Template:Bug - Group crashes by various dimensions. Within a search, it would be nice to group the crashes by things such as "top 3 stack frames" (i.e., separate out crashes by the length-3 tail of the stack", crash address. There's a bug on file for this one, too. Template:Bug
bjacob Template:Bug Make it easy to add new crashreport fields, or confirm AppNotes in its role as universal custom field (maybe just a documentation issue) Template:Bug Make 'advanced search' be able to search in any field of crash reports Template:Bug 'Advanced search' should allow using boolean charts Template:Bug Allow regular expressions in 'advanced search' Template:Bug Document/clarify what 'Crashes Per Active Daily User' means Template:Bug Per-OS top crashers lists * figuring what the top crashers are, checking that they have developers assigned on them
Ehsan Akhgari I'd like to be able to query crashstats to get aggregate data on crashes. Template:Bug, Template:Bug, Template:Bug
Brian Smith I would like a link to the zip file of the build and the necessary symbol files (if any) that corresponds to the crash, next to the link to the minidump. Also, if it is a Windows crash, then I would like the minidump to have the "dmp" extension automatically. Basically, anything that can be done to get from the crash to debugging the crash in fewer steps would be great.
Mark Banner - Crash-stats explaining itself a bit more. - comparison of rankings between releases - have new crashes been introduced, have crashes been fixed? Template:Bug - for these releases show me the crashes per ADU for the first y weeks of each of those releases normalised to the release date (with pretty graph and table).