Null-dereference READ in net::HttpCache::Writers::DoNetworkRead |
|||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5651866838630400 Fuzzer: inferno_webbot Job Type: linux_asan_chrome_media Platform Id: linux Crash Type: Null-dereference READ Crash Address: 0x000000000000 Crash State: net::HttpCache::Writers::DoNetworkRead net::HttpCache::Writers::DoLoop net::HttpCache::Writers::Read Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_media&range=552588:552589 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5651866838630400 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for instructions to reproduce this bug locally.
,
Dec 27
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/fb1ccf02ee8ca79e1404abfd3a3a7d540b7d2dbd (Make --site-per-process the default on ToT via fieldtrial_testing_config). 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.
,
Dec 27
Automatically applying components based on crash stacktrace and information from OWNERS files. If this is incorrect, please apply the Test-Predator-Wrong-Components label.
,
Dec 30
ClusterFuzz testcase 5651866838630400 appears to be flaky, updating reproducibility label.
,
Jan 12
ClusterFuzz testcase 5651866838630400 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
, Dec 27