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

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

Unable to provide possible suspect using Predator, CL and Code Search.
Could someone please look into the issue.

Thank You...

matt, is this in MediaSource bucket?

Hmm. This looks like a single huge (400MB) allocation from media::VideoFrame::AllocateMemory() from FFmpegVideoDecoder's GetVideoBuffer is triggering the OOM.

P3; will investigate later.

ClusterFuzz has detected this issue as fixed in range 583266:583305.

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

Fuzzer: libFuzzer_mediasource_MP2T_AACLC_AVC_pipeline_integration_fuzzer
Job Type: mac_libfuzzer_chrome_asan
Platform Id: mac

Crash Type: Out-of-memory (exceeds 2048 MB)
Crash Address: 
Crash State:
  mediasource_MP2T_AACLC_AVC_pipeline_integration_fuzzer
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=mac_libfuzzer_chrome_asan&range=499767:499873
Fixed: https://clusterfuzz.com/revisions?job=mac_libfuzzer_chrome_asan&range=583266:583305

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

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.

ClusterFuzz testcase 6569850645512192 is verified as fixed, so closing issue as verified.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.