crash in mozilla::a11y::DocAccessibleParent::ActorDestroy(mozilla::ipc::IProtocolManager<T>::ActorDestroyReason)

RESOLVED FIXED in Firefox 54

Status

()

--
critical
RESOLVED FIXED
3 years ago
2 years ago

People

(Reporter: davidb, Assigned: tbsaunde)

Tracking

({crash})

43 Branch
mozilla54
Unspecified
Windows NT
crash
Points:
---

Firefox Tracking Flags

(firefox51 unaffected, firefox52 unaffected, firefox53 disabled, firefox54 fixed)

Details

(crash signature)

This bug was filed from the Socorro interface and is 
report bp-8174c444-114d-495d-a038-a776f2150820.
=============================================================

Another MOZ_DIAGNOSTIC_ASSERT(CheckDocTree())

More reports here: http://is.gd/etz89F

Updated

3 years ago
Crash Signature: [@ mozilla::a11y::DocAccessibleParent::ActorDestroy(mozilla::ipc::IProtocolManager<T>::ActorDestroyReason)] → [@ mozilla::a11y::DocAccessibleParent::ActorDestroy(mozilla::ipc::IProtocolManager<T>::ActorDestroyReason)] [@ mozilla::a11y::DocAccessibleParent::ActorDestroy]

Comment 1

3 years ago
David, do you believe this is another e10s+a11y related crash? I would like to add the appropriate tracking flag if so. This is showing up at #16 spot in top crashes on DevEd44 (3 days worth of data) so definitely a concern.
Flags: needinfo?(dbolter)
(In reply to Ritu Kothari (:ritu) from comment #1)
> David, do you believe this is another e10s+a11y related crash?

Yep.
Blocks: 1029143
Flags: needinfo?(dbolter)
Please reopen if reappears.
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → WORKSFORME
There are 103 crashes on nightly 54 with buildid 20170216030210.
Status: RESOLVED → REOPENED
status-firefox54: --- → affected
Resolution: WORKSFORME → ---

Comment 6

2 years ago
Pushed by tsaunders@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/e952a5cc4a14
downgrade various MOZ_DIAGNOSTIC_ASSERTs
(Assignee)

Updated

2 years ago
Flags: needinfo?(tbsaunde+mozbugs)

Comment 7

2 years ago
bugherder
https://hg.mozilla.org/mozilla-central/rev/e952a5cc4a14
Status: REOPENED → RESOLVED
Last Resolved: 3 years ago2 years ago
status-firefox54: affected → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla54
status-firefox43: affected → ---
status-firefox51: --- → wontfix
status-firefox52: --- → affected
status-firefox53: --- → affected
NI myself to reassess for potential uplift next week.
Flags: needinfo?(dbolter)
(Assignee)

Comment 10

2 years ago
yeah lets just uplift it all.  Either it works around something or might well be needed to apply later things that do work around things.
Flags: needinfo?(tbsaunde+mozbugs)
The Firefox 52 release candidate build is being built on Monday. If we intend to uplift any of these fixes to 52 still, it needs to happen ASAP.
Assignee: nobody → tbsaunde+mozbugs
Flags: needinfo?(tbsaunde+mozbugs)
This shouldn't affect 52 except for people forcing e10s + a11y. Updating flag.
status-firefox51: wontfix → unaffected
status-firefox52: affected → unaffected
e10s+a11y isn't riding past Aurora on 53.
status-firefox53: affected → disabled
Flags: needinfo?(tbsaunde+mozbugs)
You need to log in before you can comment on or make changes to this bug.