Null-dereference READ in GURL::spec |
|||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=4666132044447744 Fuzzer: libFuzzer_appcache_fuzzer Fuzz target binary: appcache_fuzzer Job Type: libfuzzer_chrome_msan Platform Id: linux Crash Type: Null-dereference READ Crash Address: 0x000000000028 Crash State: GURL::spec content::AppCacheHost::FinishCacheSelection content::AppCacheStorageImpl::LoadCache Sanitizer: memory (MSAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=622639:622640 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4666132044447744 Issue filed automatically. See https://www.chromium.org/developers/testing/memorysanitizer#TOC-Reproducing-ClusterFuzz-Bugs for instructions to reproduce this bug locally.
,
Jan 15
Automatically adding ccs based on OWNERS file / target commit history. If this is incorrect, please add ClusterFuzz-Wrong label.
,
Jan 15
Automatically applying components based on crash stacktrace and information from OWNERS files. If this is incorrect, please apply the Test-Predator-Wrong-Components label.
,
Jan 15
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/383af630ab376efeb833e53e12e015bd6f137da8 ([AppCache] Just ignore first_party_url_ not being initialized.). 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 15
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by ClusterFuzz
, Jan 15