QA/Topcrashes: Difference between revisions

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


== Current topcrashes being tracked for beta 3 ==
== 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.


=== Core ===
{| class="fullwidth-table"
These are topcrashers that are assumed to be caused by our code.
| style="background:#efefef" | '''#'''
 
| style="background:#efefef" | '''bug'''
* {{bug|418378}} - #6 - nsGlobalWindow::SaveWindowState(nsISupports**)
| style="background:#efefef" | '''stack'''
* {{bug|391311}} – #7 - nsChromeRegistry::CheckForNewChrome
| style="background:#efefef" | '''where'''
* {{bug|418382}} - #9 - UniscribeItem::SaveGlyphs(gfxTextRun*)
| style="background:#efefef" | '''status'''
* {{bug|418381}} - #11 - HashString(nsAString_internal const&)
|-
* {{bug|418379}} - #14 - nsNavHistoryFolderResultNode::FindChildById(__int64, unsigned int*)
| 6
* {{bug|418384}} - #26 - ClientData::GetOtlTable(long, unsigned char const**, unsigned long*)
| [https://bugzilla.mozilla.org/show_bug.cgi?id=418378 418378]
* {{bug|380015}} - #37 - nsFrame::BoxReflow(nsBoxLayoutState&, nsPresContext*, nsHTMLReflowMetrics&, nsIRenderingContext*, int, int, int, int, int)
| nsGlobalWindow::SaveWindowState(nsISupports**)
 
| core
=== Extensions ===
|
These are topcrashers that are assumed to be caused by extensions.
|-
| 7
| [https://bugzilla.mozilla.org/show_bug.cgi?id=391311 391311]
| nsChromeRegistry::CheckForNewChrome
| core
|
|-
| 9
| [https://bugzilla.mozilla.org/show_bug.cgi?id=418382 418382]
| UniscribeItem::SaveGlyphs(gfxTextRun*)
| core
|
|-
| 11
| [https://bugzilla.mozilla.org/show_bug.cgi?id=418381 418381]
| HashString(nsAString_internal const&)
| core
|
|-
| 14
| [https://bugzilla.mozilla.org/show_bug.cgi?id=418379 418379]
| nsNavHistoryFolderResultNode::FindChildById(__int64, unsigned int*)
| core
|
|-
| 26
| [https://bugzilla.mozilla.org/show_bug.cgi?id=418384 418384]
| ClientData::GetOtlTable(long, unsigned char const**, unsigned long*)
| core
|
|-
| 37
| [https://bugzilla.mozilla.org/show_bug.cgi?id=380015 380015]
| nsFrame::BoxReflow(nsBoxLayoutState&, nsPresContext*, nsHTMLReflowMetrics&, nsIRenderingContext*, int, int, int, int, int)
| core
|
|}


== What do I do? ==
== What do I do? ==

Revision as of 08:23, 4 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 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
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.