sandersd@, could you please look into this change (https://chromium.googlesource.com/chromium/src/+/b5e21461a3ca9bb8e59f53870883e84c7229c47c%5E%21/media/filters/ffmpeg_demuxer.cc) if possible?

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=5368369242439680

Fuzzer: attekett_dom_fuzzer
Job Type: linux_cfi_chrome
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  CHECK failed: blocking_thread_.Start() in ffmpeg_demuxer.cc
  media::FFmpegDemuxer::Initialize
  media::PipelineImpl::StateTransitionTask
  
Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_cfi_chrome&range=385576:385614

Minimized Testcase (0.86 Kb): https://cluster-fuzz.appspot.com/download/AMIfv96RkchSZQtjS9ZGGqt9wmLB8ig99MlZl-PVArZf-yu_OfAN35EcH9K_IWpWw026itIfWe36WVK5NqFQjekeA6A9al6FAi4vDOP3m4ndAz2kl6Eiwgn1puGlnXTYXUVljkVNq8R3CjXcDUFOB_pOHICz4n97qQ

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.

Marking 'WontFix' as per c#2.

Thank you!

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