Predator did not provide any possible suspects.
Assigning to the concern owner from CL --
https://chromium.googlesource.com/chromium/src/+log/c9c18a6d62d771a20d35a5de43bfc4b33edbd818..7121fdaa21dd8bd1775f5619a7167457f6f370a6?pretty=fuller

Suspecting Commit#
https://chromium.googlesource.com/chromium/src/+/41b895907e65a2131803d93c690f8f43b67d7d7d

@ricea -- Could you please look into the issue, kindly re-assign if this is not related to your changes.
Thank You.

Note: This looks similar to Bug Id -- 750278.

Repro is the same. Does Clusterfuzz consider it a different issue because it has a different job type?

ClusterFuzz has detected this issue as fixed in range 491300:491330.

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

Fuzzer: inferno_layout_test_unmodified
Job Type: linux_lsan_chrome_mp
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000000
Crash State:
  safe_browsing::WebSocketSBHandshakeThrottle::ThrottleHandshake
  blink::DocumentWebSocketChannel::Connect
  Connect
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_lsan_chrome_mp&range=490333:490358
Fixed: https://clusterfuzz.com/revisions?job=linux_lsan_chrome_mp&range=491300:491330

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


See https://github.com/google/clusterfuzz-tools for more information.

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