QA/Talkback/Topcrash Analysis/Firefox Trunk: Difference between revisions

QA/Talkback/Topcrash Analysis/Firefox Trunk (view source)

1,012 bytes added , 21 September 2006

canmove, Confirmed users, Bureaucrats and Sysops emeriti

1,334

edits

@@ Line 6: / Line 6: @@
 == Bug Status ==
+=== nsEditor::DeleteSelectionImpl ===
+Covered by {{bug|352520}}.
+=== ntdll.dll ===
+=== nsWindow::DataToAData ===
+Covered by {{bug|332713}}.  Has simplified testcase; reproducable.
+=== 0x00000000 ===
+=== 0x772f2f3a ===
+Most crashes covered by {{bug|351468}}.
+=== libc.so.6 ===
+=== PL_DHashTableEnumerate ===
+In all crashes as of 2006-09-20, the top of the stack is:
+* PL_DHashTableEnumerate
+* nsDOMStorage::ClearAll
+These are covered by {{bug|353227}}.
+=== 0xffffff4d ===
+In all crashes, the top 3 frames are listed as:
+* 0xffffff4d
+* 0x01******
+* js_GC
+These are covered by {{bug|347053}}, which has appeared and gone away repeatedly on both trunk and 1.8 branch.  The reports when it appears are from multiple users.  More understanding of this crash is definitely needed.
+=== nsSubstring::IsDependentOn ===
+In all crashes as of 2006-09-20, these are crashes where the top of the stack is:
+* nsSubstring::Assign
+* ...something with DOM storage (write me!)...
+These are covered by {{bug|353227}}.