QA/Topcrashes: Difference between revisions
< QA
Jump to navigation
Jump to search
| Line 35: | Line 35: | ||
| | | | ||
| core | | core | ||
|- | |||
| 6 | |||
| maybe {{bug|292549}} | |||
| nsFrame::BoxReflow | |||
| | |||
| | |||
|- | |||
| 11 | |||
| {{bug|418381}} | |||
| HashString | |||
| | |||
| | |||
|} | |} | ||
Revision as of 04:29, 11 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
| # | bug | stack | where | status |
| 1 | bug 422018 | googletoolbar.dll@0x4b2f libgoogletoolbar.dylib@0x4fbd | google toolbar? core? | |
| 2, 3, 14 | bug 416521 (70%), bug 422024 (20%) | RtlEnterCriticalSection, free, arena_dalloc_small | this is what shows up when we crash in free() | |
| 4 | MultiByteToWideChar | internet download manager | always has to do with idmmzcc.dll, which some Google searches associate with internet download manager | |
| 5 | bug 422027 | jsds_ScriptHookProc | core | |
| 6 | maybe bug 292549 | nsFrame::BoxReflow | ||
| 11 | bug 418381 | HashString |
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.