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

Status: RESOLVED FIXED

(Core :: Disability Access APIs, defect)

Description

[David Bolter [:davidb] (NeedInfo me for attention)]

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

Comment 1

[Ritu Kothari (:ritu) (Inactive, please n-i to RyanVM, jcristau, or pascal)]

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.

Comment 2

[David Bolter [:davidb] (NeedInfo me for attention)]

(In reply to Ritu Kothari (:ritu) from comment #1)
> David, do you believe this is another e10s+a11y related crash?

Yep.

Comment 3

[David Bolter [:davidb] (NeedInfo me for attention)]

Please reopen if reappears.

Comment 4

[Calixte Denizet (:calixte)]

There are 103 crashes on nightly 54 with buildid 20170216030210.

Comment 5

[David Bolter [:davidb] (NeedInfo me for attention)]

Some crashes:
https://crash-stats.mozilla.com/report/index/73c6227f-9fba-4ff2-b546-6f7922170217
https://crash-stats.mozilla.com/report/index/f30bbf3d-7394-4056-8676-66fe12170217
https://crash-stats.mozilla.com/report/index/19d44d7d-90d5-422a-86de-1e92f2170217
https://crash-stats.mozilla.com/report/index/33050e56-ae96-44eb-b0d2-552562170217

Comment 6

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/mozilla-inbound/rev/e952a5cc4a14
downgrade various MOZ_DIAGNOSTIC_ASSERTs

Comment 7

[Wes Kocher (:KWierso) (Not reading bugmail; email directly if needed)]

https://hg.mozilla.org/mozilla-central/rev/e952a5cc4a14

Comment 8

[David Bolter [:davidb] (NeedInfo me for attention)]

NI myself to reassess for potential uplift next week.

Comment 9

[David Bolter [:davidb] (NeedInfo me for attention)]

As expected this signature resolved: https://crash-stats.mozilla.com/search/?signature=~mozilla%3A%3Aa11y%3A%3ADocAccessibleParent%3A%3AActorDestroy%28mozilla%3A%3Aipc%3A%3AIProtocolManager%3CT%3E%3A%3AActorDestroyReason%29&signature=~mozilla%3A%3Aa11y%3A%3ADocAccessibleParent%3A%3AActorDestroy&build_id=%3E20170217030229&date=%3E%3D2017-02-18T14%3A11%3A12.000Z&date=%3C2017-02-21T14%3A11%3A12.000Z&page=1&_sort=-date&_facets=signature&_columns=date&_columns=signature&_columns=product&_columns=version&_columns=build_id&_columns=platform#facet-signature

Trying to discern if it just moves the problem or not -- we'll likely want to uplift. Trevor what do you think?

Comment 10

[Trevor Saunders (:tbsaunde)]

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.

Comment 11

[Ryan VanderMeulen [:RyanVM]]

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.

Comment 12

[David Bolter [:davidb] (NeedInfo me for attention)]

This shouldn't affect 52 except for people forcing e10s + a11y. Updating flag.

Comment 13

[Ryan VanderMeulen [:RyanVM]]

e10s+a11y isn't riding past Aurora on 53.