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

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

Automatically adding ccs based on suspected regression changelists:

Enforce capability spec renderer <--> browser. by ben@chromium.org - https://chromium.googlesource.com/chromium/src/+/c70c0e365340a5426fa1f68f0f8c7008cb94bf5e

Don't include the tracing in gpu_memory_buffer.h by ccameron@chromium.org - https://chromium.googlesource.com/chromium/src/+/9c48d1d4786798ab90251e4131a2e808faffe525

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

Using Code Search for the file, "speech_recognition_dispatcher.cc" assigning to the concern owner because of his recent work on suspect file.

Suspect CL: https://chromium.googlesource.com/chromium/src/+/5f93cebdc920d48612d7ec612c7c7724d715d7af

maxmorin@ -- Could you please look into the issue, kindly assign it to concern owner.


Thank You.

Looks like  issue 799332  (which I'm currently looking into), but with another fuzzer. I'm leaving this one open to let both fuzzers verify the fix.

ClusterFuzz testcase 5600095348457472 appears to be flaky, updating reproducibility label.

ClusterFuzz has detected this issue as fixed in range 558140:558141.

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

Fuzzer: inferno_twister
Job Type: linux_asan_chrome_media
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  iter != handle_map_.end() in speech_recognition_dispatcher.cc
  content::SpeechRecognitionDispatcher::OnErrorOccurred
  bool IPC::MessageT<SpeechRecognitionMsg_ErrorOccurred_Meta, std::__1::tuple<int,
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_media&range=420229:420270
Fixed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_media&range=558140:558141

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

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.