Closed
Bug 491197
Opened 15 years ago
Closed 12 years ago
crash after opening filepicker in nsDocAccessible::cycleCollection::Traverse ASSERTION: nsBaseHashtable was not initialized properly
Categories
(Core :: Disability Access APIs, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: tuukka.tolvanen, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: crash)
Crash Data
Attachments
(1 file)
|
(deleted),
text/plain
|
Details |
thunderbird comm-central 2009-05-03-14Z Write, Attach, wait a few seconds. Or, find an attachment, right click, save as, wait a few seconds. ###!!! ASSERTION: nsBaseHashtable was not initialized properly.: 'this->mTable.entrySize', file ../../../dist/include/xpcom/nsBaseHashtable.h, line 183
|
Reporter | |
Comment 1•15 years ago
|
||
|
|
Reporter | |
Comment 2•15 years ago
|
||
fwiw,
(gdb) f 2
#2 0xa902d148 in nsBaseHashtable<nsPtrHashKey<void const>, nsCOMPtr<nsIAccessNode>, nsIAccessNode*>::EnumerateRead (this=0xa83ebae8, enumFunc=0xa901f4d0 <ElementTraverser>, userArg=0xbfc1f044) at ../../../dist/include/xpcom/nsBaseHashtable.h:182
182 NS_ASSERTION(this->mTable.entrySize,
(gdb) p *this
$2 = {<nsTHashtable<nsBaseHashtableET<nsPtrHashKey<const void>, nsCOMPtr<nsIAccessNode> > >> = {mTable = { ops = 0xa5a5a5a5, data = 0xa5a5a5a5, hashShift = -23131 (0xa5a5), maxAlphaFrac = 165 (0xa5) '�', minAlphaFrac = 165 '�', entrySize = 0, entryCount = 2779096485 (0xa5a5a5a5), removedCount = 2779096485, generation = 2779096485, entryStore = 0xa5a5a5a5 <Address 0xa5a5a5a5 out of bounds>}}, <No data fields>}
|
||
Comment 3•15 years ago
|
||
This is an indication of a serious bug in the a11y tree: ###!!! ASSERTION: Never ran into the same child that we started from: 'sibling', http://mxr.mozilla.org/comm-central/source/mozilla/accessible/src/atk/nsAccessibleWrap.cpp#980
Component: General → Disability Access APIs
Product: Thunderbird → Core
QA Contact: general → accessibility-apis
Summary: crash after opening filepicker [@ PL_DHashTableEnumerate] ASSERTION: nsBaseHashtable was not initialized properly → crash after opening filepicker [@ PL_DHashTableEnumerate] from [@ nsDocAccessible::cycleCollection::Traverse] ASSERTION: nsBaseHashtable was not initialized properly
|
||
Comment 4•15 years ago
|
||
I've seen this assertion in the past, too, but never had a reliable way to reproduce. Surkov, any ideas?
I think the assertion is caused by tooltip. It has been there for a long time. I think it might not be related to this crash.
|
||
Comment 6•13 years ago
|
||
Can it be reproduced nowadays? Accessibility core has been much changed for the last year.
|
Assignee | |
Updated•13 years ago
|
Crash Signature: [@ PL_DHashTableEnumerate]
[@ nsDocAccessible::cycleCollection::Traverse]
|
||
Updated•12 years ago
|
Crash Signature: [@ PL_DHashTableEnumerate]
[@ nsDocAccessible::cycleCollection::Traverse] → [@ PL_DHashTableEnumerate | nsBaseHashtable<nsPtrHashKey<XPCWrappedNative>, JSObject*, JSObject*>::EnumerateRead(PLDHashOperator (*)(XPCWrappedNative*, JSObject*, void*), void*)]
Summary: crash after opening filepicker [@ PL_DHashTableEnumerate] from [@ nsDocAccessible::cycleCollection::Traverse] ASSERTION: nsBaseHashtable was not initialized properly → crash after opening filepicker in nsDocAccessible::cycleCollection::Traverse ASSERTION: nsBaseHashtable was not initialized properly
|
||
Comment 7•12 years ago
|
||
Comment 6 is very lonely. Closing WFM, if this crash shows up the related bug will be shown as fixed, and someone should reopen it thereby answering comment 6.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•