As per the  Issue 729900  owner, assigning this issue to @xhwang.
@xhwang -- Could you please look into this issue, kindly reassign if it has nothing to do with your changes.
Thanks.

Can't repro, so guessing this is related to histogram oom.

Unduping this one since it doesn't seem improved by my CL.

dalecurtis: I won't have time looking into this any time soon, and this is not specific to EME. Is it possible to find another owner for a quicker fix? Thanks!

=>randomly assigned to hubbe@ - we've got enough of these for everyone to have one :)

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.

https://chromium.googlesource.com/chromium/third_party/ffmpeg/+/ef5c25779b2e96e8a163f2e0a343c0a08a06af0d

Patch didn't seem to resolve the OOM crash (CF stats still show it occurring 10s of times daily). Removing from being a ffmpeg roll blocker.

=>tguilbert as part of next ffmpeg roll.

ClusterFuzz has detected this issue as fixed in range 517703:517713.

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

Fuzzer: libFuzzer_media_pipeline_integration_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

Crash Type: Out-of-memory (exceeds 2048 MB)
Crash Address: 
Crash State:
  media_pipeline_integration_fuzzer
  
Sanitizer: memory (MSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=413228:413328
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=517703:517713

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

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.

I'm not sure why this could have been fixed. Rerunning task.

ClusterFuzz has detected this issue as fixed in range 517703:517713.

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

Fuzzer: libFuzzer_media_pipeline_integration_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

Crash Type: Out-of-memory (exceeds 2048 MB)
Crash Address: 
Crash State:
  media_pipeline_integration_fuzzer
  
Sanitizer: memory (MSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=413228:413328
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=517703:517713

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

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.

I'm not sure how this was fixed, but it seems it was. The fixed range includes this CL:
https://chromium.googlesource.com/chromium/src/+/aea3d2d4d8d304df1a029ef83d248508073bd066