Issue metadata
Sign in to add a comment
|
ASAN unknown exception on address 0x00000000 (pc 0x004adeca bp 0x04eacbe4 sp 0x04eacbe0 T0) |
||||||||||||||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5179272934457344 Fuzzer: inferno_twister Job Type: windows_asan_chrome_no_sandbox Platform Id: windows Crash Type: Unknown exception Crash Address: 0x00000000 Crash State: NULL Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=windows_asan_chrome_no_sandbox&range=508786:508875 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5179272934457344 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for more information.
,
Oct 15 2017
,
Oct 15 2017
This is a serious security regression. If you are not able to fix this quickly, please revert the change that introduced it. If this doesn't affect a release branch, or has not been properly classified for severity, please update the Security_Impact or Security_Severity labels, and remove the ReleaseBlock label. To disable this altogether, apply ReleaseBlock-NA. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 15 2017
,
Oct 18 2017
,
Oct 19 2017
Cluster-fuzz appears to be no longer able to reproduce this.
,
Jan 27 2018
This bug has been closed for more than 14 weeks. Removing security view restrictions. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||
Comment 1 by elawrence@chromium.org
, Oct 15 2017