Closed Bug 429639 Opened 12 years ago Closed 11 years ago
Crash [@ ns
XULListbox Accessible::~ns XULListbox Accessible() ]
Three crashes that happened with beta 5. One of the reports indicates the address bar/Location bar. http://crash-stats.mozilla.com/report/list?range_unit=weeks&query_search=signature&query_type=contains&product=Firefox&platform=windows%2Cmac%2Clinux&version=Firefox%3A3.0b5%2CFirefox%3A3.0pre&branch=1.9&signature=nsXULListboxAccessible%3A%3A~nsXULListboxAccessible()&query=Access&range_value=1
Hard to block with only three crashes. Please re-nom if you disagree.
Flags: blocking1.9? → blocking1.9-
They pointed to http://bonsai.mozilla.org/cvsblame.cgi?file=mozilla/accessible/src/xul/nsXULSelectAccessible.h&rev=1.35&mark=111#111. Why do we keep empty virtual destructors at all?
Alexander, anything else we want to do on this one? It still appeared a couple of times in b5 over the past week.
Mass un-assigning bugs assigned to Aaron.
Assignee: aaronleventhal → nobody
Is this bug stale? Alexander, not sure of your question but virtual destructors are generally recommended (in case subclasses or subsubclasses ... have special cleanup to do)
I mean no one of our destructors makes anything, all of them are empty iirc. So I can't see a reason to keep them.
11 years ago
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
Crash Signature: [@ nsXULListboxAccessible::~nsXULListboxAccessible() ]
You need to log in before you can comment on or make changes to this bug.