Direct-leak in dri2_initialize_surfaceless |
|||||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5127325614866432 Fuzzer: libFuzzer_chromeos_virgl_fuzzer Job Type: libfuzzer_asan_chromeos Platform Id: linux Crash Type: Direct-leak Crash Address: Crash State: dri2_initialize_surfaceless dri2_initialize _eglMatchDriver Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_asan_chromeos&range=2801419:2801745 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5127325614866432 Issue filed automatically. See https://chromium.googlesource.com/chromiumos/docs/+/master/fuzzing.md#Reproducing-crashes-from-ClusterFuzz for more information.
,
Nov 7
,
Nov 28
,
Nov 30
,
Dec 1
ClusterFuzz testcase 5127325614866432 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 4
ClusterFuzz testcase 5127325614866432 appears to be flaky, updating reproducibility label.
,
Dec 4
Please ignore the last comment about testcase being unreproducible. The testcase is still reproducible. This was caused by another bug in ClusterFuzz that has been fixed. Sorry again for the inconvenience. |
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by ClusterFuzz
, Oct 27Labels: ClusterFuzz-Auto-CC