Direct-leak in blink::scheduler::WebTaskRunnerImpl::Create |
|||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5381083825963008 Fuzzer: libFuzzer_renderer_fuzzer Job Type: libfuzzer_chrome_asan Platform Id: linux Crash Type: Direct-leak Crash Address: Crash State: blink::scheduler::WebTaskRunnerImpl::Create blink::scheduler::WebFrameSchedulerImpl::GetTaskRunner blink::LocalFrame::GetTaskRunner Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=520881:520896 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5381083825963008 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
,
Jan 14 2018
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/e7ea91203b8c29c7327355f8289107026fb63418 (Worker: Reject dynamic import() on WorkerGlobalScope with informative message). If this is incorrect, please remove the owner and apply the Test-Predator-Wrong-CLs label.
,
Jan 15 2018
Looks like my change is not relevant. hajimehoshi@,altimin@: Can you take a look?
,
Jan 15 2018
Given that it's also base::internal::WeakReferenceOwner::GetRef and blink::UserMediaClient::Create which are leaking and DocumentLoader appears in all leaks I suggest that it's a loading issue. +Loading team
,
Feb 19 2018
ClusterFuzz testcase 5381083825963008 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
, Jan 14 2018Labels: Test-Predator-Auto-Components