Direct-leak in content::ResourceDispatcher::StartAsync |
|||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5441296819552256 Fuzzer: inferno_layout_test_unmodified Job Type: linux_lsan_chrome_mp Platform Id: linux Crash Type: Direct-leak Crash Address: Crash State: content::ResourceDispatcher::StartAsync content::WebURLLoaderImpl::Context::Start content::WebURLLoaderImpl::LoadAsynchronously Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=linux_lsan_chrome_mp&range=512182:512192 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5441296819552256 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for more information.
,
Jan 30 2018
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/04f27c37974050559508833241e11258fb8c1a4a (Replace base::MakeUnique with std::make_unique in content/.). If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.
,
Feb 20 2018
ClusterFuzz testcase 5441296819552256 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 30 2018Labels: Test-Predator-Auto-Components