Direct-leak in dri2_initialize_surfaceless |
|||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5129516264194048 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=5129516264194048 Issue filed automatically. See https://chromium.googlesource.com/chromiumos/docs/+/master/fuzzing.md#Reproducing-crashes-from-ClusterFuzz for more information.
,
Aug 1
This shouldn't be occurring because there is a suppression for eglInitialize based allocations. Essentially to get a good balance of performance and avoiding other memory leaks, I chose to take the one time leak of eglInitialize resources when implementing the fuzzer.
,
Aug 31
,
Aug 31
davidriley: this sounds like it's a WontFix? Please reopen if I'm misunderstanding comment #2.
,
Sep 5
I thought that metzman@ was investigating why the suppressions were not properly working which should fix this issue.
,
Sep 5
Sorry, this seems to have slipped my mind. I will try to take a look this week or next.
,
Sep 12
ClusterFuzz testcase 5129516264194048 appears to be flaky, updating reproducibility label.
,
Sep 12
ClusterFuzz testcase 5129516264194048 is flaky and no longer crashes, so closing issue. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by ClusterFuzz
, Aug 1Labels: ClusterFuzz-Auto-CC