Null-dereference WRITE in base::win::ForceCrashOnSigAbort |
||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=4843832285069312 Fuzzer: ifratric-browserfuzzer-v3 Job Type: windows_asan_chrome Platform Id: windows Crash Type: Null-dereference WRITE Crash Address: 0x00000000 Crash State: base::win::ForceCrashOnSigAbort raise sk_abort_no_print Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=windows_asan_chrome&range=479886:479938 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4843832285069312 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for more information.
,
Aug 16 2017
we are not getting reproducible crashes out of this fuzzer- closing to reduce noise and focus on those we can repro + fix
,
Aug 21 2017
ClusterFuzz has detected this issue as fixed in range 495551:495853. Detailed report: https://clusterfuzz.com/testcase?key=4843832285069312 Fuzzer: ifratric-browserfuzzer-v3 Job Type: windows_asan_chrome Platform Id: windows Crash Type: Null-dereference WRITE Crash Address: 0x00000000 Crash State: base::win::ForceCrashOnSigAbort raise sk_abort_no_print Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=windows_asan_chrome&range=479886:479938 Fixed: https://clusterfuzz.com/revisions?job=windows_asan_chrome&range=495551:495853 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4843832285069312 See https://github.com/google/clusterfuzz-tools for more information. If you suspect that the result above is incorrect, try re-doing that job on the test case report page. |
||
►
Sign in to add a comment |
||
Comment 1 by msrchandra@chromium.org
, Jul 27 2017Labels: M-62 Test-Predator-Wrong