QA/Topcrashes: Difference between revisions
Samuelsidler (talk | contribs) (New page: '''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...) |
Samuelsidler (talk | contribs) (→Core: I hate wikis.) |
||
| Line 8: | Line 8: | ||
These are topcrashers that are assumed to be caused by our code. | These are topcrashers that are assumed to be caused by our code. | ||
#6 - nsGlobalWindow::SaveWindowState(nsISupports**) | {{bug|418378}} - #6 - nsGlobalWindow::SaveWindowState(nsISupports**) | ||
#9 - UniscribeItem::SaveGlyphs(gfxTextRun*) | {{bug|418382}} - #9 - UniscribeItem::SaveGlyphs(gfxTextRun*) | ||
#11 - HashString(nsAString_internal const&) | {{bug|418381}} - #11 - HashString(nsAString_internal const&) | ||
#14 - nsNavHistoryFolderResultNode::FindChildById(__int64, unsigned int*) | {{bug|418379}} - #14 - nsNavHistoryFolderResultNode::FindChildById(__int64, unsigned int*) | ||
#26 - ClientData::GetOtlTable(long, unsigned char const**, unsigned long*) | {{bug|418384}} - #26 - ClientData::GetOtlTable(long, unsigned char const**, unsigned long*) | ||
=== Extensions === | === Extensions === | ||
Revision as of 07:57, 3 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
Core
These are topcrashers that are assumed to be caused by our code.
bug 418378 - #6 - nsGlobalWindow::SaveWindowState(nsISupports**) bug 418382 - #9 - UniscribeItem::SaveGlyphs(gfxTextRun*) bug 418381 - #11 - HashString(nsAString_internal const&) bug 418379 - #14 - nsNavHistoryFolderResultNode::FindChildById(__int64, unsigned int*) bug 418384 - #26 - ClientData::GetOtlTable(long, unsigned char const**, unsigned long*)
Extensions
These are topcrashers that are assumed to be caused by extensions.
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.