Open Bug 1330930 Opened 4 years ago Updated 3 years ago
Enhance crash data to diagnose mozilla::gmp::GMPChild::Processing
Error crashes .
Bug 1273372 and friends have all been for a generic crash (in mozilla::gmp::GMPChild::ProcessingError) that has normally been caused by the sandbox blocking the load of the DLL. (But it could be caused by other failures as well.) Because the blocking is just done by the OS and we crash later on, we don't get much information about what the root cause might be. Generally we've relied on reproducing user reports and taking it from there. We've added logging in the past to facilitate this. We should try and enhance the crash data to help diagnose or at least categorise these crashes.
FYI looks like we have the same crash as an intermittent test failure in Treeherder now: bug 1330949
See Also: → 1330949
(In reply to Nils Ohlmeier [:drno] from comment #1) > FYI looks like we have the same crash as an intermittent test failure in > Treeherder now: bug 1330949 This instance is likely a regression from Bug 1318965, which was backed out after this failure was logged.
Crash volume for signature 'mozilla::gmp::GMPChild::ProcessingError': - nightly (version 54): 161 crashes from 2017-01-23. - aurora (version 53): 33 crashes from 2017-01-23. - beta (version 52): 215 crashes from 2017-01-23. - release (version 51): 159 crashes from 2017-01-16. - esr (version 45): 0 crashes from 2016-08-10. Crash volume on the last weeks (Week N is from 02-06 to 02-12): W. N-1 W. N-2 W. N-3 W. N-4 W. N-5 W. N-6 W. N-7 - nightly 89 43 - aurora 29 0 - beta 120 43 - release 95 29 0 - esr 0 0 0 0 0 0 0 Affected platforms: Windows, Mac OS X, Linux Crash rank on the last 7 days: Browser Content Plugin - nightly #4 - aurora #15 - beta #8217 #33 - release #33 - esr
Mass change P2->P3 to align with new Mozilla triage process.
Priority: P2 → P3
You need to log in before you can comment on or make changes to this bug.