Closed
Bug 1206165
Opened 9 years ago
Closed 9 years ago
crash in mozilla::a11y::DocAccessible::UpdateTreeOnRemoval(mozilla::a11y::Accessible*, nsIContent*)
Categories
(Core :: Disability Access APIs, defect)
Tracking
()
RESOLVED
FIXED
mozilla44
People
(Reporter: davidb, Assigned: surkov)
References
Details
(Keywords: crash)
Crash Data
Attachments
(1 file, 1 obsolete file)
883 bytes,
patch
|
davidb
:
review+
|
Details | Diff | Splinter Review |
This bug was filed from the Socorro interface and is report bp-78ed3630-e310-4854-a5ee-dab402150918. ============================================================= More here: https://crash-stats.mozilla.com/report/list?product=Firefox&signature=mozilla%3A%3Aa11y%3A%3ADocAccessible%3A%3AUpdateTreeOnRemoval%28mozilla%3A%3Aa11y%3A%3AAccessible%2A%2C+nsIContent%2A%29
Assignee | ||
Comment 1•9 years ago
|
||
that should make a trick
Assignee: nobody → surkov.alexander
Attachment #8663287 -
Flags: review?(dbolter)
Reporter | ||
Comment 2•9 years ago
|
||
Comment on attachment 8663287 [details] [diff] [review] patch Review of attachment 8663287 [details] [diff] [review]: ----------------------------------------------------------------- ::: accessible/generic/DocAccessible.cpp @@ +2057,5 @@ > nsTArray<nsIContent*>* childEls = it.UserData(); > for (uint32_t idx = 0; idx < childEls->Length(); idx++) { > nsIContent* childEl = childEls->ElementAt(idx); > Accessible* child = GetAccessible(childEl); > + if (child && child->IsInDocument() && !child->GetFrame()) { OK... was the problem that the child was orphaned?
Attachment #8663287 -
Flags: review?(dbolter) → review+
Assignee | ||
Comment 3•9 years ago
|
||
(In reply to David Bolter [:davidb] from comment #2) > OK... was the problem that the child was orphaned? that's working assumption
Comment 5•9 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/793589a533f1
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla43
Backout: https://hg.mozilla.org/releases/mozilla-aurora/rev/ecf66181845e
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
I'm not sure how this bug should end up since I backed out this, bug 1205476, and bug 1133213 on Aurora but not on trunk.
Flags: needinfo?(surkov.alexander)
Assignee | ||
Comment 8•9 years ago
|
||
it should be marked as fixed in Firefox 44
Status: REOPENED → RESOLVED
Closed: 9 years ago → 9 years ago
Flags: needinfo?(surkov.alexander)
Resolution: --- → FIXED
Target Milestone: mozilla43 → mozilla44
This still happens in 44 build 0924, e.g. bp-829c36d3-45cd-4d72-808d-e8d472150924
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 10•9 years ago
|
||
(Is "status-firefox43: fixed" correct? Seems like it should be "affected", but since I don't know the details around the backout, I'm leaving it alone)
status-firefox44:
--- → affected
Assignee | ||
Comment 11•9 years ago
|
||
Attachment #8663287 -
Attachment is obsolete: true
Attachment #8666885 -
Flags: review?(dbolter)
Reporter | ||
Updated•9 years ago
|
Attachment #8666885 -
Flags: review?(dbolter) → review+
Comment 13•9 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/215f91248653
Status: REOPENED → RESOLVED
Closed: 9 years ago → 9 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•