Difference between revisions of "Viewer Crash Reporting"
Jump to navigation
Jump to search
Ramzi Linden (talk | contribs) |
|||
| Line 1: | Line 1: | ||
[[Category:Linden Lab Projects]] | |||
= Objectives = | = Objectives = | ||
* Report all crashes properly (opt-out available) | * Report all crashes properly (opt-out available) | ||
| Line 7: | Line 9: | ||
Studio Shiny has committed to making the Second Life viewer more stable. This involves finding and fixing viewer crashes. We have found that the existing crash reporter doesn't help us as much as it should. It doesn't always give us the data we need to investigate crash patterns, doesn't scale to SL's current size, doesn't always report a crash, in fact, sometimes the crash reporter itself crashes. | Studio Shiny has committed to making the Second Life viewer more stable. This involves finding and fixing viewer crashes. We have found that the existing crash reporter doesn't help us as much as it should. It doesn't always give us the data we need to investigate crash patterns, doesn't scale to SL's current size, doesn't always report a crash, in fact, sometimes the crash reporter itself crashes. | ||
= | = Phase 1 = | ||
* Create central library of crash reporter functionality | * Create central library of crash reporter functionality | ||
* Get near 100% of all crashes reported with the call stack included | * Get near 100% of all crashes reported with the call stack included | ||
= Phase 2 = | |||
* Refinements to the crash reporter functionality | |||
** properly capture crashes before login or viewer initialization | |||
= See Also = | = See Also = | ||
* [[Viewer Roadmap]] | * [[Viewer Roadmap]] | ||
Revision as of 17:21, 31 March 2008
Objectives
- Report all crashes properly (opt-out available)
- Make crash report processing automatic and immediate
- Make crash report data useful
Motivation
Studio Shiny has committed to making the Second Life viewer more stable. This involves finding and fixing viewer crashes. We have found that the existing crash reporter doesn't help us as much as it should. It doesn't always give us the data we need to investigate crash patterns, doesn't scale to SL's current size, doesn't always report a crash, in fact, sometimes the crash reporter itself crashes.
Phase 1
- Create central library of crash reporter functionality
- Get near 100% of all crashes reported with the call stack included
Phase 2
- Refinements to the crash reporter functionality
- properly capture crashes before login or viewer initialization