Predator and CL did not provide any possible suspect.
Using Code Search for the file, "checks.cc" assigning to the concern owner.
Suspecting Commit#
https://chromium.googlesource.com/external/webrtc/trunk/webrtc.git/+/16378411c456de1d6b11acf309fca1ba63150049

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

ClusterFuzz has detected this issue as fixed in range 472211:472281.

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

Fuzzer: phoglund_webrtc_peerconnection
Job Type: windows_asan_chrome_no_sandbox
Platform Id: windows

Crash Type: Null-dereference WRITE
Crash Address: 0x00000000
Crash State:
  base::win::ForceCrashOnSigAbort
  rtc::FatalMessage::~FatalMessage
  cricket::TransportController::CreateDtlsTransport_n
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=windows_asan_chrome_no_sandbox&range=472181:472211
Fixed: https://clusterfuzz.com/revisions?job=windows_asan_chrome_no_sandbox&range=472211:472281

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


Additional requirements: Requires Gestures

Additional requirements: Requires HTTP

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 5786362380025856 is verified as fixed, so closing issue.

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