Predator and CL could not provide any possible suspects.
Assigning to concern owner who might be related or worked on similar type of fuzzer (media_vpx_video_decoder_fuzzer)

@mmoroz -- Could you please look into the issue, kindly re-assign if this is not related to your changes.
Thank You.

ClusterFuzz is analyzing your testcase. Developers can follow the progress at https://clusterfuzz.com/testcase?key=5501022394122240.

Let's try to reproduce it with ASan. OOMs with MSan are not always valid...

Doesn't crash with ASan, though takes for a while to perform 100 runs:

$ out/Release/media_vpx_video_decoder_fuzzer -print_final_stats=1 -timeout=25 -rss_limit_mb=2048 -runs=100 ./clusterfuzz-testcase-minimized-4537370514030592 
INFO: Seed: 4265735722
INFO: Loaded 2 modules (414358 guards): [0x7ff3c49614a0, 0x7ff3c497c3f4), [0x33db6e0, 0x35551e4), 
<...>/out/Release/media_vpx_video_decoder_fuzzer: Running 1 inputs 100 time(s) each.
Running: ./clusterfuzz-testcase-minimized-4537370514030592
#2	pulse  cov: 977 ft: 682 exec/s: 1 rss: 724Mb
#4	pulse  cov: 977 ft: 682 exec/s: 1 rss: 725Mb
#8	pulse  cov: 977 ft: 682 exec/s: 1 rss: 725Mb
#16	pulse  cov: 977 ft: 684 exec/s: 1 rss: 725Mb
#32	pulse  cov: 982 ft: 689 exec/s: 1 rss: 725Mb
#64	pulse  cov: 983 ft: 690 exec/s: 1 rss: 725Mb
Executed ./clusterfuzz-testcase-minimized-4537370514030592 in 97239 ms
***
*** NOTE: fuzzing was not performed, you have only
***       executed the target code on a fixed set of inputs.
***
stat::number_of_executed_units: 100
stat::average_exec_per_sec:     1
stat::new_units_added:          0
stat::slowest_unit_time_sec:    0
stat::peak_rss_mb:              725

Could be related to  issue 767336 , but not sure.

For more information, please see https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md.

The link referenced in the description is no longer valid.

(bulk edit)

 Issue 801916  has been merged into this issue.

ClusterFuzz testcase 4917745111269376 is still reproducing on tip-of-tree build (trunk).

If this testcase was not reproducible locally or unworkable, ignore this notification and we will file another bug soon with hopefully a better and workable testcase.

Otherwise, if this is not intended to be fixed (e.g. this is an intentional crash), please add ClusterFuzz-Ignore label to prevent future bug filing with similar crash stacktrace.

 Issue 806454  has been merged into this issue.

 Issue 807563  has been merged into this issue.

 Issue 812103  has been merged into this issue.

 Issue 813031  has been merged into this issue.

 Issue 814283  has been merged into this issue.

 Issue 815501  has been merged into this issue.