This bug was filed from the Socorro interface and is report bp-64777aa1-390c-4210-a5ab-8556c2170127. ============================================================= This looks like a new crash as of January 25. Same function as bug 1334058, but a different error message. It looks like this is a result of bug 1332690 added more information to a failure.
Maybe you can make some use of this crash information, Trevor.
Crash volume for signature 'IPCError-browser | PDocAccessibleParent::RecvShowEvent invalid index': - nightly (version 54): 530 crashes from 2017-01-23. - aurora (version 53): 0 crashes from 2017-01-23. - beta (version 52): 0 crashes from 2017-01-23. - release (version 51): 0 crashes from 2017-01-16. - esr (version 45): 0 crashes from 2016-08-03. Crash volume on the last weeks (Week N is from 01-30 to 02-05): W. N-1 W. N-2 W. N-3 W. N-4 W. N-5 W. N-6 W. N-7 - nightly 324 - aurora 0 - beta 0 - release 0 0 - esr 0 0 0 0 0 0 0 Affected platform: Windows Crash rank on the last 7 days: Browser Content Plugin - nightly #5 - aurora - beta - release - esr
Created attachment 8832897 [details] [diff] [review] ignore some invalid Show event messages I'm not having much luck debugging this, so lets disable these checks for now and only crash when we hit a more serious problem, hopefully that'll make things more usable for people with touch screens till we disable a11y there.
10 months ago
Pushed by firstname.lastname@example.org: https://hg.mozilla.org/integration/mozilla-inbound/rev/03f88e289233 ignore some invalid Show event messages r=davidb
If I understand correctly, this is just a mutation of an existing crash signature? Do we need to uplift this to Aurora then too?
This crash signature only shows up in 54. Looks like bug 1332690 may be related but work there just landed and was backed out.
we should probably uplift the work around. Its not great, but fixes some crashes.
Please request Aurora approval in that case.
e10s+a11y isn't riding past Aurora on 53.