Null-dereference READ in content::AppCacheHost::host_id |
||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5679679381700608 Fuzzer: libFuzzer_appcache_fuzzer Fuzz target binary: appcache_fuzzer Job Type: libfuzzer_chrome_msan Platform Id: linux Crash Type: Null-dereference READ Crash Address: 0x000000000018 Crash State: content::AppCacheHost::host_id content::AppCacheUpdateJob::NotifySingleHost content::AppCacheUpdateJob::StartUpdate Sanitizer: memory (MSAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=623461:623463 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5679679381700608 Issue filed automatically. See https://www.chromium.org/developers/testing/memorysanitizer#TOC-Reproducing-ClusterFuzz-Bugs 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)
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/2761bb080c9f9c2a84614616e851ed2dc1c669d9 ([AppCache] ReportBadMessage rather than DCHECK for preconditions on mojo API.). 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.
,
Jan 19
(3 days ago)
|
||||
►
Sign in to add a comment |
||||
Comment 1 by ClusterFuzz
, Jan 17 (5 days ago)Labels: Test-Predator-Auto-Components