Bad Lock in media::ChunkDemuxerStream::SetEnabled |
||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=6041723146076160 Fuzzer: ochang_domfuzzer Job Type: linux_tsan_chrome_mp Platform Id: linux Crash Type: Null-dereference READ Crash Address: 0x000000000050 Crash State: __GI___pthread_mutex_lock base::internal::LockImpl::Lock media::ChunkDemuxerStream::SetEnabled Sanitizer: thread (TSAN) Regressed: https://clusterfuzz.com/revisions?job=linux_tsan_chrome_mp&range=518240:518474 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6041723146076160 Additional requirements: Requires HTTP Issue filed automatically. See https://github.com/google/clusterfuzz-tools for more information.
,
Dec 26 2017
Predator and CL could not provide any possible suspects. Using Code Search for the file, "lock_impl_posix.cc" assigning to the concern owner who might be related. Suspect CL: https://chromium.googlesource.com/chromium/src/+/62ae282c378bd6658c877bf3a9e911e41764ec32 bcwhite@ -- Could you please look into the issue, kindly re-assign if this is not related to your changes. Thank You.
,
Jan 2 2018
kkaluri, If lock gets a SEGV, it's not the lock-code's fault but the caller. Looking through the CL range, there are several media/ changes. The first one seems an option crashes in tests... https://chromium-review.googlesource.com/783640 audio: Change FakeAudioOutputStream to derive from MuteableAudioOutputStream.
,
Jan 27 2018
ClusterFuzz testcase 6041723146076160 is flaky and no longer crashes, so closing issue. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue. |
||||
►
Sign in to add a comment |
||||
Comment 1 by ClusterFuzz
, Dec 25 2017Labels: Test-Predator-Auto-Components