inferno@, is there any thing we can do? please close if it is not valid.
Thank you.

mbarbella@, could you please take a look?.

Could some one please look into the issue and provide an update so that the issue could be triaged further.
Thanks in Advance.

as far as i can tell there's nothing at all useful (such as a stack trace) in the detailed report.

ClusterFuzz has detected this issue as fixed in range 477612:477627.

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

Fuzzer: attekett_surku_fuzzer
Job Type: linux_lsan_chrome_mp
Platform Id: linux

Crash Type: Direct-leak
Crash Address: 
Crash State:
  g_malloc
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_lsan_chrome_mp&range=316457:316488
Fixed: https://clusterfuzz.com/revisions?job=linux_lsan_chrome_mp&range=477612:477627

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


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.

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

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