diff options
author | dalecurtis <dalecurtis@chromium.org> | 2015-12-11 12:29:19 -0800 |
---|---|---|
committer | Commit bot <commit-bot@chromium.org> | 2015-12-11 20:30:00 +0000 |
commit | 24a953e9db68003b25262936d8ddf20bf251aeb3 (patch) | |
tree | 462a7e5586878bdad8a6c09e3b22b1c0d6cbc7e8 /docs/linux_development.md | |
parent | c12347847f52a0338339b2b9cbf77ae15cc86943 (diff) | |
download | chromium_src-24a953e9db68003b25262936d8ddf20bf251aeb3.zip chromium_src-24a953e9db68003b25262936d8ddf20bf251aeb3.tar.gz chromium_src-24a953e9db68003b25262936d8ddf20bf251aeb3.tar.bz2 |
Convert audio thread hang crash to UMA. Dump driver info on Win.
This crash has gone on for too long and, as far as we know, can't
be fixed within Chrome. So instead of crashing just log this data
to UMA on all platforms. On Windows dump a non-crash report
with the device driver name and version information since we have
an open channel with Microsoft for tracking down misbehaving drivers.
Introduces a new histogram Media.AudioThreadStatus for tracking
started, hung, and recovered values. As well as code for reading
the driver name and version from dxdiag structures.
Notably, since this is now a UMA we will record hangs even on
stable or beta, but only log crash dumps on Dev/Canary/Unknown;
since these hangs appear to be high frequency, it doesn't seem
wise or necessary to enable the crash dumps on stable/beta. If
canary/unknown prove sufficient for crash key dumps, I'll limit
to there in a followup CL.
BUG=422522,478932,546750
TEST=new unittest, manual verification of uma values.
TBR=thestig
Review URL: https://codereview.chromium.org/1513143002
Cr-Commit-Position: refs/heads/master@{#364792}
Diffstat (limited to 'docs/linux_development.md')
0 files changed, 0 insertions, 0 deletions