QA/Firefox3/TestResults/RC1/RC2BugCandidates: Difference between revisions

QA/Firefox3/TestResults/RC1/RC2BugCandidates (view source)

Revision as of 21:30, 22 May 2008

1,931 bytes added , 22 May 2008

m

→‎Bug Candidates for Triage

Tchung

Confirmed users

6,361

edits

@@ Line 28: / Line 28: @@
 * Confirming during FFT: {{Bug|324334}} - Cannot switch to Error Console in the "Window" menu
 * {{Bug|419928}} – Add "InstallerLocation" for Java in PFS. PFS is broken on production, stuck in infinite loop.  Webdev fix by adding a manual install option.
+;Crashers
 * {{bug|433525}} - crash [@ nsNavHistoryQueryResultNode::IsContainersQuery()].   Number 1 topcrash, is a recent regression which we should probably respin for. The bug has a patch ready to go.
 * {{Bug|434401}} – crash [@ gfxWindowsFont::GetOrMakeFont(FontEntry*, gfxFontStyle const*)]. that may be happening in thebes or layout. dbaron believes thebes.
 * {{Bug|434403}} – startup crash [@ nsDocShell::SetupNewViewer(nsIContentViewer*)]. recent regression. While we saw this crash in beta 5 (presumably from upgrading from beta 4), it's much greater this release and happens at a different address.
+;Accessibility
+* {{Bug|432970}} - Shutdown() of
+nsXULTooltipAccessible is not called. Affects Linux only, but can cause
+accessible tree corruption because tooltip accessibles from tabs that
+are already closed may still be around and accidentally accessed by the
+Orca screen reader. Again not a blocker, but a good candidate to tag along.
+* {{Bug|434002}} - event show
+isn't fired for treecol accessible. This is an embarrassing oversight
+from review of fix for {{bug|413777}}. It basically means that event_show is
+never ever called for any accessible even if it needs to be. The most
+obvious use case we found isn't in Firefox but Thunderbird, when column
+* {{Bug|432467}} - firefox
+segfaults in plone kupu editor [@ nsDocAccessible::FlushPendingEvents].
+This is a crasher reported by the RedHat folks that indicates a race
+condition between two things trying to release the same accessible. See
+comment #4 for the description. Assessment of risk is also in the bug. I
+wouldn't respin for this, but if it could tag along if RC2 is being done
+anyway, that would be very good I think. This can happen with other
+ajax-enabled stuff as well.
+* {{Bug|432869}} - Divide by zero
+in IsProbablyForLayout(). This came up while triaging crash-stats. It is
+a simple check for certain types of layout tables to make sure we never
+divide by zero. Was probably missed during review of another bug's
+patch. Again, for safety reasons, it would be good to have this, but not
+blocking the release if 3.0.1 is only 4 to 6 weeks away after that.
+headers of the message trees change when switching from folder to
+folder. But this can happen to any extension suing tree tables in
+Firefox and replacing one view with another and changing column headers,
+and it can happen to some types of Ajax-empowered web sites, leading to
+accessible tree corruptions. Again not a blocker per se, but again a
+good candidate to ride along on an RC2 build.