could this be a flake, it looks like a really weird stack?

mbarbella, mmoroz: Do either of you have any thoughts on what is going on here? I have no idea what to make of this report.

ClusterFuzz has detected this issue as fixed in range 473820:473831.

Detailed report: https://clusterfuzz.com/testcase?key=6312644184375296

Fuzzer: cdiehl_dharma
Job Type: linux_asan_chrome_chromeos
Platform Id: linux

Crash Type: Heap-buffer-overflow READ {*}
Crash Address: 0x7fe653eac800
Crash State:
  __printf_chk
  
Sanitizer: address (ASAN)

Recommended Security Severity: Low

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_chromeos&range=466203:466237
Fixed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_chromeos&range=473820:473831

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6312644184375296


Additional requirements: Requires Gestures

See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.

Ken, it does really look flaky, and now ClusterFuzz decided that it's fixed, so nothing to do here :)

ClusterFuzz testcase 6312644184375296 is verified as fixed, so closing issue.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.

This bug has been closed for more than 14 weeks. Removing security view restrictions.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot