Issue metadata
Sign in to add a comment
|
Unknown exception in C:\windows\SYSTEM32\KERNELBASE.dll |
||||||||||||||||||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=4535738460012544 Fuzzer: inferno_layout_test_unmodified Job Type: windows_asan_chrome_no_sandbox Platform Id: windows Crash Type: Unknown exception Crash Address: 0x0570bf8c Crash State: C:\windows\SYSTEM32\KERNELBASE.dll sw::allocate sw::Surface::lockInternal Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=windows_asan_chrome_no_sandbox&range=480776:480824 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4535738460012544 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for more information.
,
Aug 23 2017
,
Aug 23 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
,
Aug 23 2017
,
Aug 23 2017
+awhalley@(Security TPM)
,
Aug 25 2017
Mind taking a look or helping to route this, sugoi@? Thanks!
,
Aug 25 2017
,
Aug 29 2017
,
Aug 29 2017
This is just a regular out-of-memory situation. We could use nothrow to silence the exception, but then we'd probably just crash on accessing the null buffer. We have no immediate intention to harden against every possible OOM. Crashing the GPU process is reasonable under exceptional situations like these. OOMs caused by leaks or allocating too much memory are a different story of course. So I'm inclined to close this as Won't Fix.
,
Sep 6 2017
,
Oct 18 2017
,
Oct 24 2017
ClusterFuzz has detected this issue as fixed in range 510178:510722. Detailed report: https://clusterfuzz.com/testcase?key=4535738460012544 Fuzzer: inferno_layout_test_unmodified Job Type: windows_asan_chrome_no_sandbox Platform Id: windows Crash Type: Unknown exception Crash Address: 0x00ccceac Crash State: C:\windows\SYSTEM32\KERNELBASE.dll sw::allocate sw::Surface::lockInternal Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=windows_asan_chrome_no_sandbox&range=480776:480824 Fixed: https://clusterfuzz.com/revisions?job=windows_asan_chrome_no_sandbox&range=510178:510722 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4535738460012544 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.
,
Oct 24 2017
ClusterFuzz testcase 4535738460012544 is verified as fixed, so closing issue as verified. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
,
Oct 24 2017
,
Dec 4 2017
,
Jan 30 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
, Aug 22 2017