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

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

Predator and CL could not provide any possible suspects.

Using Code Search for the file, "ffmpeg_demuxer.cc" suspecting the below Cl might have caused this issue

Suspect CL: https://chromium.googlesource.com/chromium/src/+/4ca53dec2e2711a6861d52f12b06b42abaea48f4

tmathmeyer@ -- Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner.

Thanks!

I don't think that change had anything to do with this clusterfuzz crash, but I am probably a right person to look at this. I'll see what I can do.

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

commit 44d5ef3148c5461893c5b77012a9046f37b69c20
Author: Ted Meyer <tmathmeyer@chromium.org>
Date: Fri Oct 12 00:15:54 2018

Increment the track ID to ensure unique IDs.

In the case of a corrupt media files where tracks are not unique, we
need to ensure that map entries are. It isn't sufficient to let ffmpeg
handle this, since it will sometimes report duplicates:
https://clusterfuzz.com/v2/testcase-detail/6184666533724160?noredirect=1
where both the audio and video track have a default track_id of 1.

Bug:  877847 
Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel
Change-Id: I7e2bc16b39c5d23e9310463c54c9f3cba8bdbfa5
Reviewed-on: https://chromium-review.googlesource.com/c/1269446
Commit-Queue: Ted Meyer <tmathmeyer@chromium.org>
Reviewed-by: Dale Curtis <dalecurtis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#599030}
[modify] https://crrev.com/44d5ef3148c5461893c5b77012a9046f37b69c20/media/filters/ffmpeg_demuxer.cc

ClusterFuzz has detected this issue as fixed in range 599022:599034.

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

Fuzzer: libFuzzer_media_pipeline_integration_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  track_id_to_demux_stream_map_.find(media_track->id()) == track_id_to_demux_strea
  media::FFmpegDemuxer::OnFindStreamInfoDone
  void base::internal::FunctorTraits<void
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=444427:444575
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=599022:599034

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

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

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