Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.

I'll take a look.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/6465f049facda4b49d5ef07090687b18830700d6

commit 6465f049facda4b49d5ef07090687b18830700d6
Author: Guido Urdaneta <guidou@chromium.org>
Date: Tue Aug 07 18:11:04 2018

Replace CHECK with CHECK_EQ in MediaStreamManager.

This CHECK should be removed since it is being hit in rare cases.
This first CL is to try to gather more information in clustefuzz
reports about the state when the CHECK is hit, since we have been
unable to reproduce it locally.
The CHECK will be removed in a follow-up CL.

Bug: 871714
Change-Id: Iefed096801002e8f4d022723c07c876ff10b0014
Reviewed-on: https://chromium-review.googlesource.com/1165542
Reviewed-by: Florent Castelli <orphis@chromium.org>
Commit-Queue: Guido Urdaneta <guidou@chromium.org>
Cr-Commit-Position: refs/heads/master@{#581282}
[modify] https://crrev.com/6465f049facda4b49d5ef07090687b18830700d6/content/browser/renderer_host/media/media_stream_manager.cc

ClusterFuzz has detected this issue as fixed in range 581289:581290.

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

Fuzzer: inferno_layout_test_unmodified
Job Type: linux_msan_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: memory (MSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_msan_chrome&range=565324:565335
Fixed: https://clusterfuzz.com/revisions?job=linux_msan_chrome&range=581289:581290

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

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 4620695783604224 is verified as fixed, so closing issue as verified.

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

Reopening this bug. Clusterfuzz marked it as fixed because a CL landed that Disable launch of the audio service on startup, but the underlying bug is still there.
Lowering priority to 2, though.