CHECK failure: !connected. AppCacheBackend::GetStatusCallback was destroyed without first eithe |
||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5740384181026816 Fuzzer: libFuzzer_appcache_fuzzer Fuzz target binary: appcache_fuzzer Job Type: libfuzzer_chrome_asan_debug Platform Id: linux Crash Type: CHECK failure Crash Address: Crash State: !connected. AppCacheBackend::GetStatusCallback was destroyed without first eithe blink::mojom::AppCacheBackend_GetStatus_ProxyToResponder::OnIsConnectedComplete void base::internal::FunctorTraits<void Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=605707:605715 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5740384181026816 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for instructions to reproduce this bug locally.
,
Jan 17
(5 days ago)
Automatically adding ccs based on OWNERS file / target commit history. If this is incorrect, please add ClusterFuzz-Wrong label.
,
Jan 17
(5 days ago)
,
Jan 19
(3 days ago)
mek@: Can you please take a look? |
||||
►
Sign in to add a comment |
||||
Comment 1 by ClusterFuzz
, Jan 17 (5 days ago)Labels: Test-Predator-Auto-Components