might be a suspected cl

https://chromium.googlesource.com/chromium/src/+/b5e21461a3ca9bb8e59f53870883e84c7229c47c%5E%21/media/filters/ffmpeg_demuxer.cc

sandersd@ could you please look into this. Thanks in advance 

Running out of threads is the expected result of creating a new <audio> element every 2ms. While we may take steps to protect against this in the future, it is not a priority at this time.

ClusterFuzz has detected this issue as fixed in range 410757:410843.

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

Fuzzer: inferno_layout_test_unmodified
Job Type: linux_asan_chrome_v8_arm
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  blocking_thread_.Start() in ffmpeg_demuxer.cc
  media::FFmpegDemuxer::Initialize
  media::PipelineImpl::RendererWrapper::StateTransitionTask
  
Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_asan_chrome_v8_arm&range=376889:376931
Fixed: https://cluster-fuzz.appspot.com/revisions?job=linux_asan_chrome_v8_arm&range=410757:410843

Unminimized Testcase: https://cluster-fuzz.appspot.com/download/AMIfv97FOhyuzng-dU7-w5d5MI2N1OagePAnxY1hmPlyXCQ1QSLAcJIiRJsMQ0JfHkW3WYYQ3m5W8rZ82b5WvgWqVGpNkm801HxCZH2hO0E3LoDSoAKc0f_-X8TWw0bxtencv4x4quBQwWlHDMg_ejDBQS62XZ8FZDhGgPJGdDCUSCYEoG123cQ?testcase_id=4679055849029632


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.

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