Code search on file media_stream_dispatcher_host.cc, suspected CL is
https://chromium.googlesource.com/chromium/src/+/da330facfb86b325030fef9bc7cf4f85930b6d16
guidou@, could you please take a look and reassign if it is not related your changes.

Thank you

ClusterFuzz has detected this testcase as flaky and is unable to reproduce it in the original crash revision. Skipping fixed testing check and marking it as potentially fixed.

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

Fuzzer: ipc_fuzzer_gen
Job Type: windows_asan_chrome_ipc
Platform Id: windows

Crash Type: CHECK failure
Crash Address: 
Crash State:
  it != device_change_subscribers_.end() in media_stream_dispatcher_host.cc
  content::MediaStreamDispatcherHost::OnCancelDeviceChangeNotifications
  IPC::MessageT<MediaStreamHostMsg_CancelDeviceChangeNotifications_Meta,std::tuple
  
Regressed: https://cluster-fuzz.appspot.com/revisions?job=windows_asan_chrome_ipc&range=401526:401543

Minimized Testcase (0.10 Kb): https://cluster-fuzz.appspot.com/download/AMIfv97hodccOktjPKDB_MRyFMMJ6UapaTJDpLzeGd_NzH9BNUxlc-qXBze9YKePoe8XelYAZBa0RZ9YJCRjjOnlNSG2IbsCIFURfDz3q44v8VCdNngzZ_jPvRVhAV3mNnbjwZFZxAsMmjIWUzEpkpTwLUClgvc_qQ?testcase_id=5940010864082944

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.

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

Fuzzer: ipc_fuzzer_gen
Job Type: windows_asan_chrome_ipc
Platform Id: windows

Crash Type: CHECK failure
Crash Address: 
Crash State:
  it != device_change_subscribers_.end() in media_stream_dispatcher_host.cc
  content::MediaStreamDispatcherHost::OnCancelDeviceChangeNotifications
  IPC::MessageT<MediaStreamHostMsg_CancelDeviceChangeNotifications_Meta,std::tuple
  
Regressed: https://cluster-fuzz.appspot.com/revisions?job=windows_asan_chrome_ipc&range=401970:402059

Minimized Testcase (0.10 Kb): https://cluster-fuzz.appspot.com/download/AMIfv96lmyXrFg67768POPEv6C7JNcDsKhEwA8r3CmLwB8D62BtD36iFVuTjz0c56vtzxK5F7By6bEMn8UZ1ZKBmdsRZlaOM5Y3Dm-nOVVDcAshGVDAPxge-q_ykzjKlRVs5zZKvBs5tPcKKSsip6erLlwm8HeZImg?testcase_id=5524517036490752

Filer: mmohammad

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

ClusterFuzz has detected this testcase as flaky and is unable to reproduce it in the original crash revision. Skipping fixed testing check and marking it as potentially fixed.

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

Fuzzer: ipc_fuzzer_gen
Job Type: windows_asan_chrome_ipc
Platform Id: windows

Crash Type: CHECK failure
Crash Address: 
Crash State:
  it != device_change_subscribers_.end() in media_stream_dispatcher_host.cc
  content::MediaStreamDispatcherHost::OnCancelDeviceChangeNotifications
  IPC::MessageT<MediaStreamHostMsg_CancelDeviceChangeNotifications_Meta,std::tuple
  
Regressed: https://cluster-fuzz.appspot.com/revisions?job=windows_asan_chrome_ipc&range=401970:402059

Minimized Testcase (0.10 Kb): https://cluster-fuzz.appspot.com/download/AMIfv96lmyXrFg67768POPEv6C7JNcDsKhEwA8r3CmLwB8D62BtD36iFVuTjz0c56vtzxK5F7By6bEMn8UZ1ZKBmdsRZlaOM5Y3Dm-nOVVDcAshGVDAPxge-q_ykzjKlRVs5zZKvBs5tPcKKSsip6erLlwm8HeZImg?testcase_id=5524517036490752

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.

As per comment#2, and #4, marking the bug as wontfix.

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