Predator and CL could not provide any possible suspects.

Using Code Search for the file, "media_stream_manager.cc" suspecting the below Cl might have caused this issue

Suspect CL: https://chromium.googlesource.com/chromium/src/+/814d076a9365c16da0ad910244526484b6e586dd

guidou@ -- Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner.

Thanks!

I can't reproduce this issue with any build, including the ubsan/vptr builds referenced in http://www.chromium.org/developers/testing/undefinedbehaviorsanitizer.

Will check again after landing a fix for a different, but maybe related crash.

ClusterFuzz has detected this issue as fixed in range 572625:572626.

Detailed report: https://clusterfuzz.com/testcase?key=5626791579090944

Fuzzer: inferno_layout_test_unmodified
Job Type: linux_ubsan_vptr_chrome
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  request->state(device.type) == MEDIA_REQUEST_STATE_OPENING in media_stream_manag
  content::MediaStreamManager::Opened
  content::AudioInputDeviceManager::OpenedOnIOThread
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_chrome&range=565325:565335
Fixed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_chrome&range=572625:572626

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5626791579090944

See https://github.com/google/clusterfuzz-tools 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 5626791579090944 is verified as fixed, so closing issue as verified.

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