{"id":59,"date":"2008-04-21T09:37:41","date_gmt":"2008-04-21T17:37:41","guid":{"rendered":"http:\/\/blog.mozilla.org\/webdev\/2008\/04\/21\/crash-analysis-now-in-open-source-flavor\/"},"modified":"2017-03-08T14:50:14","modified_gmt":"2017-03-08T22:50:14","slug":"crash-analysis-now-in-open-source-flavor","status":"publish","type":"post","link":"https:\/\/blog.mozilla.org\/webdev\/2008\/04\/21\/crash-analysis-now-in-open-source-flavor\/","title":{"rendered":"Crash Analysis: now in Open Source flavor"},"content":{"rendered":"

History can tell you that companies don’t disclose crashes in their software. They keep a pretty close eye on what crashes and bugs are disclosed.<\/p>\n

Mozilla doesn’t.<\/p>\n

Rather than being the exception, openness is the rule, and that is one of the coolest things about being a part of this. My job, my everday tasks, they aren’t secret, and they are not to drive profits. They are to drive the web.<\/p>\n

\"soccorro<\/p>\n

In that spirit, our crash reporting system<\/a> (Socorro<\/a>) is available to whoever wants to view it. Aside from user-bound statistics, crash information is available in full and anybody in the community can learn about where in the code their client crashed. They can also help provide hints or comments about what they were doing at the time they crashed.<\/p>\n

This opens the door for the community to learn valuable things about their software and how they use it:<\/p>\n