Regression CL ::
================
https://chromium.googlesource.com/chromium/src/+log/53adfa415fbf9bcb34a1e988b83da7d42a1b4cf9..1c88977a803343e486b591443e8edc65b90c25fa?pretty=fuller

Possible suspect 
https://codereview.chromium.org/2122153002

perkj@ Could you please look into this issue if it is related to your change,else please route this to an appropriate owner for this issue.

Thanks,

I have only changed test files so its not me in that range. 
Olga, do you know anything about this? I can't see anything that sticks out in that range.

Looks like we are getting zero as hardware buffer size here https://cs.chromium.org/chromium/src/third_party/WebKit/Source/platform/audio/AudioDestination.cpp?sq=package:chromium&dr=CSs&rcl=1468293534&l=70

I don't know of any recent change that could cause it though, and have not found any place where it can be set to 0 so far. The value is obtained from browser side (audio manager) via synchronous IPC.

"Unable to reproduce crash reliably" sounds suspicious.

Moving this nonessential bug to the next milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Generally when we see 0 values it's because there's no audio hardware. Previously we had checks in place for 0 value sample rates that may have been lost in recent refactorings.

There is no hardware on those VMs. Tried to track down recent changes, but have not found checks. Should we CHECK in AudioHardwareConfig?

No, clients need to check that the config given to them is valid before trying to use it. When this happens on media we fallback to a fake audio renderer.

ClusterFuzz has detected this issue as fixed in range 404886:404895.

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=5082153218211840

Fuzzer: phoglund_webrtc_peerconnection
Job Type: linux_asan_chrome_chromeos
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  frames > 0 in audio_bus.cc
  media::ValidateConfig
  media::AudioBus::AudioBus
  
Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_asan_chrome_chromeos&range=403894:403906
Fixed: https://cluster-fuzz.appspot.com/revisions?job=linux_asan_chrome_chromeos&range=404886:404895

Unminimized Testcase: https://cluster-fuzz.appspot.com/download/AMIfv95-TWTr9zItUVwaDf19gt0_syYHpL-tUXDQXrAlvluIb5NmSlOnuXg3ONRCigNUpsm_TSKNKXVY1KvmyapjCT_CVY5mW-E5SHj5lUxivwHIY3ES8l2OMKCoKxV81JliBhQuq4NsvI43gsRPNxmVhHb3lXDsevl9zDeVrHRsRKlC4zeh-EI?testcase_id=5082153218211840


Additional requirements: Requires Gestures

Additional requirements: Requires HTTP

See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.

ClusterFuzz testcase is verified as fixed, closing issue.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.

Checking for no device is being tracked in  Issue 549125 .

Removing EditIssue view restrictions from ClusterFuzz filed bugs. If you believe that this issue should still be restricted, please reapply the label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot