Providing Findit results for internal purpose:
Suspected CLs	Findit could not determine the memory tool from the stacktrace. Is it in a new format?

unable to find the culprit, assigning to https://cs.chromium.org/chromium/src/ui/OWNERS

sadrul@, sky@, thakis@ - Could you please check the above issue & help us in finding an owner it its not yours.

Looks like a bad ack from a renderer could crash the browser. We should probably kill the renderer instead. Over to input-dev folks.

chongz@ can you take a look?

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=4797697072824320

Fuzzer: ipc_fuzzer_mut
Job Type: linux_cfi_chrome_ipc
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  !terminated_ in latency_info.cc
  ui::LatencyInfo::AddLatencyNumberWithTimestampImpl
  ui::LatencyInfo::AddLatencyNumber
  
Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_cfi_chrome_ipc&range=398946:399285

Minimized Testcase (290.97 Kb): https://cluster-fuzz.appspot.com/download/AMIfv97F1hoaNw1oaYrigGJ0K9_F4IHE8RuB5S2oDsFyeYlWI8XIbkaeQDbTqNdCsXcWXV803ps9M5KY8RKE5bkezIXtc6FXIJdV8NvBY-Bn-duqXR3z605GJbJpuzsuKJpFJ-6frTMCcMwPVF351NXZ4VtAFr5FiC9fky9BRcqyvtxj3ilCKnE?testcase_id=4797697072824320

Filer: rnimmagadda

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

Removing EditIssue view restrictions from ClusterFuzz filed bugs. If you believe that this issue should still be restricted, please reapply the label.

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

ClusterFuzz testcase 4797697072824320 is flaky and no longer reproduces, so closing issue.

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