QA/Topcrashes: Difference between revisions
< QA
Jump to navigation
Jump to search
ChrisHofmann (talk | contribs) |
ChrisHofmann (talk | contribs) |
||
| Line 74: | Line 74: | ||
| HashString | | HashString | ||
| | | | ||
|looks like a start-up crash. not much to go on for further investigation. running the | |looks like a start-up crash. not much to go on for further investigation. running the mini-dump might help. | ||
|- | |- | ||
| 12 | | 12 | ||
| Line 83: | Line 83: | ||
|- | |- | ||
| 16 | | 16 | ||
| 0x0 | | [http://crash-stats.mozilla.com/report/list?product=Firefox&query_search=signature&query_type=contains&range_unit=weeks&version=Firefox%3A3.0b4&signature=%400x0&range_value=1 0x0 ] | ||
| | | | ||
| didn't find any common patterns in sample of ten; this is mixed crashes (although about half the stacks are useless) -[[User:Dbaron|David Baron]] | | didn't find any common patterns in sample of ten; this is mixed crashes (although about half the stacks are useless) -[[User:Dbaron|David Baron]] | ||
Revision as of 04:05, 13 March 2008
In progress. I have a lot more work to do on this page.
This page is a tracking document for handling and following topcrashes on the trunk.
Current topcrashes being tracked for beta 4
data for beta4 crashes in the last week
| # | bug | stack | where | status |
| 1 | bug 422018 | googletoolbar.dll@0x4b2f libgoogletoolbar.dylib@0x4fbd | google toolbar? core? | |
| 2, 3, 14, 17 | bug 416521 (70%), bug 422024 (20%) | RtlEnterCriticalSection, free, arena_dalloc_small, ntdll.dll@0x42e7b | this is what shows up when we crash in free() | bug 422024 is related to scriptable plugin API |
| 4 | tried to block IDM extension in bug 382356 but it's still showing up. | MultiByteToWideChar | internet download manager | always has to do with idmmzcc.dll, which some Google searches associate with internet download manager - |
| 5, 15 | bug 421303 | jsds_ScriptHookProc | Fixed for 2008-03-11 builds | |
| 6 | maybe bug 292549 or bug 380015 | nsFrame::BoxReflow | ||
| 7 | bug 421217 | JS_SetPrivate | silverlight plugin or scriptable plugin API | |
| 8, 13 | bug 419695 | js_GetGCThingTraceKind, JS_CallTracer, JS_TraceChildren | crashing on yahoo mail (maybe not all of the JS_CallTracer crashes, though?) | Fixed for 2008-03-12 builds |
| 9 | bug 391311 | nsChromeRegistry::CheckForNewChrome | ||
| 10 | bug 418384 | ClientData::GetOtlTable | has testcase (requires particular font) | |
| 11 | bug 418381 | HashString | looks like a start-up crash. not much to go on for further investigation. running the mini-dump might help. | |
| 12 | bug 422467 | piclens.dll | the piclens extension | the extension doesn't appear to be compatible, or marked as such (although it can't be installed due to not providing secure updates), and the crash is what you'd expect from using a binary extension with incompatible interface changes. Is this entirely from people overriding extension compat? -- piclens develpers contacted 3/12 |
| 16 | 0x0 | didn't find any common patterns in sample of ten; this is mixed crashes (although about half the stacks are useless) -David Baron | ||
| 18 | bug 418382 | UniscribeItem::SaveGlyphs(gfxTextRun*) | core | |
| 19 (2 on mac) | bug 421294 | DocumentViewerImpl::GetCopyable | fixed for 2008-03-07 builds |
Current topcrashes being tracked for beta 3
Topcrashers for beta3 are currently considered "old". We need to re-track for beta4. I'm using this "old" data as sample data to see if what format works.
| # | bug | stack | where | status |
| 4 | 405357 | jpinscp.dll@0xcf45 | java plugin | |
| 6 | 418378 | nsGlobalWindow::SaveWindowState(nsISupports**) | core | |
| 7 | 391311 | nsChromeRegistry::CheckForNewChrome | core | |
| 9 | 418382 | UniscribeItem::SaveGlyphs(gfxTextRun*) | core | |
| 11 | 418381 | HashString(nsAString_internal const&) | core | |
| 14 | 418379 | nsNavHistoryFolderResultNode::FindChildById(__int64, unsigned int*) | core | |
| 26 | 418384 | ClientData::GetOtlTable(long, unsigned char const**, unsigned long*) | core | |
| 37 | 380015 | nsFrame::BoxReflow(nsBoxLayoutState&, nsPresContext*, nsHTMLReflowMetrics&, nsIRenderingContext*, int, int, int, int, int) | core |
What do I do?
So, someone CCed you to a topcrash bug and asked for your help. What should you do?
There are several steps that developers and QA need to go through to help fix a crash. As a developer, we're specifically asking that you comment in the bug when you've completed all the steps and specifically state which steps you completed.