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

Automatically applying components based on information from OWNERS files. If this seems incorrect, please apply the Test-Predator-Wrong-Components label.

Ditto on distribution.

Taking this one

Thanks for taking on this one, Thomas.

Thanks Thomas!

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.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/7912f2d5d66cdfa61d3d006f7944474077435142

commit 7912f2d5d66cdfa61d3d006f7944474077435142
Author: Thomas Guilbert <tguilbert@chromium.org>
Date: Tue Oct 09 00:45:07 2018

Fix webm ContentEncodings DCHECK

This CL changes a DCHECK into a parser error.

Bug:  768470 
Change-Id: Ica195722a25d992b897c37be6f245e6d93cfa9c5
Reviewed-on: https://chromium-review.googlesource.com/c/1269812
Commit-Queue: Thomas Guilbert <tguilbert@chromium.org>
Reviewed-by: Chrome Cunningham <chcunningham@chromium.org>
Cr-Commit-Position: refs/heads/master@{#597757}
[modify] https://crrev.com/7912f2d5d66cdfa61d3d006f7944474077435142/media/formats/webm/webm_tracks_parser.cc

ClusterFuzz has detected this issue as fixed in range 597748:597757.

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

Fuzzer: libFuzzer_mediasource_WEBM_VORBIS_pipeline_integration_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  !track_content_encodings_client_.get() in webm_tracks_parser.cc
  media::WebMTracksParser::OnListStart
  media::WebMListParser::OnListStart
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=499783:499873
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=597748:597757

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

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 5689031848624128 is verified as fixed, so closing issue as verified.

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