Closed
Bug 429639
Opened 17 years ago
Closed 15 years ago
Crash [@ nsXULListboxAccessible::~nsXULListboxAccessible() ]
Categories
(Core :: Disability Access APIs, defect)
Tracking
()
RESOLVED
WORKSFORME
mozilla1.9
People
(Reporter: MarcoZ, Unassigned)
References
Details
(Keywords: access, crash)
Crash Data
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
Flags: blocking1.9?
Comment 1•17 years ago
|
||
Hard to block with only three crashes. Please re-nom if you disagree.
Flags: blocking1.9? → blocking1.9-
Comment 2•17 years ago
|
||
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?
Reporter | ||
Comment 3•17 years ago
|
||
Alexander, anything else we want to do on this one? It still appeared a couple of times in b5 over the past week.
Comment 5•15 years ago
|
||
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)
Comment 6•15 years ago
|
||
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.
Updated•15 years ago
|
Severity: major → critical
Updated•15 years ago
|
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → WORKSFORME
Assignee | ||
Updated•14 years ago
|
Crash Signature: [@ nsXULListboxAccessible::~nsXULListboxAccessible() ]
You need to log in
before you can comment on or make changes to this bug.
Description
•