CF really thinks wants to blame you due to https://codereview.chromium.org/2108003002 but this looks like a refactor? Can you help here?

I recall mcasas@ ran into a similar crash. This shouldn't happen because serviceConnectionError() is bound with wrapWeakPersistent().

ClusterFuzz has detected this issue as fixed in range 420372:420502.

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

Fuzzer: inferno_layout_test_unmodified
Job Type: linux_asan_chrome_mp
Platform Id: linux

Crash Type: UNKNOWN READ
Crash Address: 0x7eb798aceb48
Crash State:
  mojo::internal::Router::OnConnectionError
  mojo::Connector::HandleError
  mojo::Connector::OnWatcherHandleReady
  
Recommended Security Severity: Low

Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_asan_chrome_mp&range=407005:407057
Fixed: https://cluster-fuzz.appspot.com/revisions?job=linux_asan_chrome_mp&range=420372:420502

Minimized Testcase (7.75 Kb): https://cluster-fuzz.appspot.com/download/AMIfv97lqXxRr3vbKSs9N4YHv37w_B_s_AnaEeZZ4XqIqMlcrLElSPN8n9TR8G2PKA4qL_dRHRdMb21U5uTBezOYJYBg5yFZZh34jq5sSuA1mVEQ74jd6xPaJvWtuYH6dS5O4tDxKVuwjY58IaopeDvfn_N-Kw1maQ?testcase_id=5460312558141440

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 is verified as fixed, 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