QA/Topcrashes: Difference between revisions

From MozillaWiki
< QA
Jump to navigation Jump to search
Line 2: Line 2:


This page is a tracking document for handling and following topcrashes on the trunk.
This page is a tracking document for handling and following topcrashes on the trunk.
== Current topcrashes being tracked for beta 4 ==
{| class="fullwidth-table"
| style="background:#efefef" | '''#'''
| style="background:#efefef" | '''bug'''
| style="background:#efefef" | '''stack'''
| style="background:#efefef" | '''where'''
| style="background:#efefef" | '''status'''
|-
| 1
| {{bug|422018}
| googletoolbar.dll@0x4b2f libgoogletoolbar.dylib@0x4fbd
| google toolbar?  core?
|
|}


== Current topcrashes being tracked for beta 3 ==
== Current topcrashes being tracked for beta 3 ==

Revision as of 03:34, 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 422018} googletoolbar.dll@0x4b2f libgoogletoolbar.dylib@0x4fbd google toolbar? core?

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.