Data race in read_frame_internal |
|||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5427164494430208 Fuzzer: ochang_domfuzzer Job Type: linux_tsan_chrome_mp Platform Id: linux Crash Type: Data race READ 4 Crash Address: 0x7b5c0002fed4 Crash State: read_frame_internal av_read_frame base::internal::Invoker<base::internal::BindState<int Sanitizer: thread (TSAN) Regressed: https://clusterfuzz.com/revisions?job=linux_tsan_chrome_mp&range=466318:466320 Reproducer Testcase: https://clusterfuzz.com/download/AMIfv97tIMiZnq970msN7MAjXTDeEKtiD-t3tEmZE35_Ko-YyutpT4oy3NAinEjo5vWuw_2esoZVHWrX0doKqu3-IBE_1nABNa0JBv4jibMmHS9Cuh18Y8jb4jjUW04tk6JHkydAuUiRjMiiuzQQ7wTKJcBqfqm4jBXT1voZeu0o2XZprOZhROex_hjytGmrWUEOw82dpH3NDJnMTc3aZDDbO7b2GuAQCNoIdXtsjTFdJm5yjSGIXTBCqoWQyWVDsmbc69YspoGHaESRHv1Zd4YMJXCVojtkWXZKP_wWDGulp50IOrCGv8Hd-FwK4IE6AQujN7lPpQ9GsthOidFy1G7Hh9StQBGJz8aKGBx4Ygp_Scxdd8oq-RA?testcase_id=5427164494430208 Additional requirements: Requires Gestures Issue filed automatically. See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.
,
Apr 22 2017
ClusterFuzz has detected this issue as fixed in range 466472:466488. Detailed report: https://clusterfuzz.com/testcase?key=5427164494430208 Fuzzer: ochang_domfuzzer Job Type: linux_tsan_chrome_mp Platform Id: linux Crash Type: Data race READ 4 Crash Address: 0x7b5c0002fed4 Crash State: read_frame_internal av_read_frame base::internal::Invoker<base::internal::BindState<int Sanitizer: thread (TSAN) Regressed: https://clusterfuzz.com/revisions?job=linux_tsan_chrome_mp&range=466318:466320 Fixed: https://clusterfuzz.com/revisions?job=linux_tsan_chrome_mp&range=466472:466488 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5427164494430208 Additional requirements: Requires Gestures 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.
,
Apr 22 2017
ClusterFuzz testcase 5427164494430208 is verified as fixed, so closing issue. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
,
Apr 24 2017
I don't think this is actually fixed => servolk@, it seems like we're calling SetEnabled on the wrong thread, it must be trampolined to the blocking thread.
,
Apr 24 2017
IIRC the problem is that we are setting AVStream.discard property on media thread (see https://cs.chromium.org/chromium/src/media/filters/ffmpeg_demuxer.cc?rcl=7ddccb994a410a624be528ca2143c869afb67683&l=743). It probably doesn't make sense to call all of SetEnabled on the FFmpeg thread, we'd just get the opposite problem of accessing FFmpegDemuxerStream properties from non-media thread. Instead we can probably just post the setting of AVStream.discard to the blocking_task_runner_. The discard property is purely an optimization thing, so it should be ok if it's updated slightly after the SetEnabled has been toggled. I'll make a CL.
,
Apr 24 2017
,
Apr 24 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/12b000b53d9f17fe443e7ff10a57f00f9ff17045 commit 12b000b53d9f17fe443e7ff10a57f00f9ff17045 Author: servolk <servolk@chromium.org> Date: Mon Apr 24 23:00:46 2017 Set FFmpeg AVStream discard on FFmpeg task runner thread BUG= 714217 Review-Url: https://codereview.chromium.org/2836173002 Cr-Commit-Position: refs/heads/master@{#466809} [modify] https://crrev.com/12b000b53d9f17fe443e7ff10a57f00f9ff17045/media/filters/ffmpeg_demuxer.cc [modify] https://crrev.com/12b000b53d9f17fe443e7ff10a57f00f9ff17045/media/filters/ffmpeg_demuxer.h
,
Apr 24 2017
,
Sep 18 2017
We have made a bunch of changes on ClusterFuzz side, so resetting ClusterFuzz-Wrong label. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by mummare...@chromium.org
, Apr 22 2017Components: Internals>Media>FFmpeg
Labels: M-60 Test-Predator-Wrong