Out-of-memory in swiftshader_vertex_routine_fuzzer |
|||||||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=6644155089682432 Fuzzer: libFuzzer_swiftshader_vertex_routine_fuzzer Job Type: libfuzzer_chrome_asan Platform Id: linux Crash Type: Out-of-memory (exceeds 2048 MB) Crash Address: Crash State: swiftshader_vertex_routine_fuzzer Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=529743:529752 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6644155089682432 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
,
Aug 24
There is a swiftshader roll inside regression range.
,
Aug 24
,
Aug 24
,
Oct 9
,
Oct 10
,
Oct 26
,
Dec 1
ClusterFuzz testcase 6644155089682432 appears to be flaky, updating reproducibility label.
,
Dec 1
Please ignore the last comment about testcase being unreproducible. The testcase is still reproducible. This happened due to a code refactoring on ClusterFuzz side, and the underlying root cause is now fixed. Resetting the label back to Reproducible. Sorry about the inconvenience caused from these incorrect notifications.
,
Dec 1
Please ignore the last comment about testcase being unreproducible. The testcase is still reproducible. This happened due to a code refactoring on ClusterFuzz side, and the underlying root cause is now fixed. Resetting the label back to Reproducible. Sorry about the inconvenience caused from these incorrect notifications.
,
Dec 17
|
|||||||||||
►
Sign in to add a comment |
|||||||||||
Comment 1 by kkaluri@chromium.org
, Aug 9Components: Internals>GPU>SwiftShader
Labels: M-69 Test-Predator-Wrong CF-NeedsTriage