Indirect-leak in allocateRaw |
|||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5709689405571072 Fuzzer: inferno_layout_test_unmodified Job Type: linux_lsan_chrome_mp Platform Id: linux Crash Type: Indirect-leak Crash Address: Crash State: allocateRaw sw::allocate Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=linux_lsan_chrome_mp&range=495528:495712 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5709689405571072 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for more information.
,
Jul 23
Since it related to Swiftshader component, assigning it to capn@ for further triage.
,
Aug 2
Couldn't reproduce a crash, and the clusterfuzz reproduce tool claims that this result matched the original report. Also, the report doesn't have a stack trace that I can work with. I suspect a ClusterFuzz issue.
,
Aug 9
ClusterFuzz testcase 5709689405571072 is still reproducing on tip-of-tree build (trunk). If this testcase was not reproducible locally or unworkable, ignore this notification and we will file another bug soon with hopefully a better and workable testcase. Otherwise, if this is not intended to be fixed (e.g. this is an intentional crash), please add ClusterFuzz-Ignore label to prevent future bug filing with similar crash stacktrace.
,
Aug 16
ClusterFuzz testcase 5709689405571072 appears to be flaky, updating reproducibility label. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by ClusterFuzz
, Jul 21Labels: Test-Predator-Auto-Components