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

Suspecting Commit#
https://chromium.googlesource.com/chromium/src/+/9e34bfe4ec5a706f31689ede21c752b6fb82e071

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

I believe this was fixed by https://codereview.webrtc.org/2915263002. Can't repro on latest chrome.

ClusterFuzz has detected this issue as fixed in range 480271:480453.

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

Fuzzer: inferno_layout_test_unmodified
Job Type: linux_asan_chrome_v8_arm
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x00000000
Crash State:
  webrtc::WebRtcSession::GetCallStats
  rtc::FunctorMessageHandler<webrtc::Call::Stats, rtc::MethodFunctor<webrtc::WebRt
  jingle_glue::JingleThreadWrapper::Dispatch
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_v8_arm&range=476918:476985
Fixed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_v8_arm&range=480271:480453

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


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.