Direct-leak in GLSLFastFuzzTask |
||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5156738015428608 Fuzzer: libFuzzer_dawn_spirv_cross_msl_fast_fuzzer Job Type: libfuzzer_chrome_asan Platform Id: linux Crash Type: Direct-leak Crash Address: Crash State: GLSLFastFuzzTask DawnSPIRVCrossFuzzer::ExecuteWithSignalTrap GLSLFastFuzzTask Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=609745:609751 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5156738015428608 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
,
Nov 21
Automatically assigning owner based on suspected regression changelist https://dawn.googlesource.com/dawn/+/fbeca676d409ec19572e3299288f4010c2ee8fd5 (Tighten when signal trap is used in SPIRV-Cross fuzzers). If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.
,
Nov 23
,
Dec 1
ClusterFuzz testcase 5156738015428608 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 4
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by ClusterFuzz
, Nov 21Labels: ClusterFuzz-Auto-CC