The result is a list of CLs that change the crashed files. 

Author: dalecurtis
Project: chromium
Changelist: https://chromium.googlesource.com/chromium/src/+/5384b9fe1cf67869e1bf98ab8ff6bd21ae4216da
Time: Tue Feb 28 02:34:28 2017
Lines 877-882 of file ffmpeg_demuxer.cc which potentially caused crash are changed in this cl (frame #1, "media::FFmpegDemuxer::~FFmpegDemuxer").
Minimum distance from crash line to modified line: 0. (file: ffmpeg_demuxer.cc, crashed on: 877, modified: 877).

This change was reverted. I'll fix resolve this before relanding.

ClusterFuzz has detected this issue as fixed in range 453545:453565.

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=5943228881960960

Fuzzer: inferno_flicker
Job Type: linux_tsan_chrome_mp
Platform Id: linux

Crash Type: Data race WRITE 8
Crash Address: 0x7b3c00000b48
Crash State:
  media::FFmpegDemuxer::~FFmpegDemuxer
  media::WebMediaPlayerImpl::~WebMediaPlayerImpl
  blink::HTMLMediaElement::invokeLoadAlgorithm
  
Sanitizer: thread (TSAN)

Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_tsan_chrome_mp&range=453417:453487
Fixed: https://cluster-fuzz.appspot.com/revisions?job=linux_tsan_chrome_mp&range=453545:453565

Reproducer Testcase: https://cluster-fuzz.appspot.com/download/AMIfv96lCxhOMxHjvYBGy01FWAtgyZljIHAPzURElX7UJGygj4WCreYcld1vi-R5IsRV1_PWBKeoDV0-L7BbaZhjH33sZG2q3ZIyLKXKfhBAgOUgNOlZMDsPnt7XmVCR0jR_xfj_egI6oKNStcO_8T7axEFiVMLs-eQ1gcacfyR9PFSpTUcQMDgDyg82dTT3sRCG2Rku6swqyrIjtvVxXb7dpRQndQlEWGL5CCKuxTlRfS4m35XW4b7jUgfwz3WDN8SvbtkWnBqawTlO20OcCy2f09Ru6uy3qNqER6H7FiN90HXlBBXJCZuVuBMY10dfWKatYHUs-Q0n-DiHdC6g2q3GUZ1pwCQl00we-xU9v00pcWt6BIKydKsMOEHpGAGuk9UBVsoN3aaboVg24Ktrj8kENaecLWeevA?testcase_id=5943228881960960


See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs 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 5943228881960960 is verified as fixed, so closing issue.

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