Predator and CL could not provide any possible suspects.
Using Code Search for the file, "peerconnection.cc" assigning to the concern owner.

Suspecting Commit#
https://chromium.googlesource.com/external/webrtc/trunk/webrtc.git/+/7a02da194b1d07675e94383b10bd157158c0cb21

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

I think this is the same issue as https://bugs.chromium.org/p/chromium/issues/detail?id=757830#c8  which should already been fixed by this CL: https://codereview.webrtc.org/3006723002

The revision range is 496121:496160 which doesn't contains my fix CL so the crash is expected. Could you please verify that it doesn't happen in the latest revision? If so, I think we should be able to close the issue.

ClusterFuzz has detected this issue as fixed in range 496287:501540.

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

Fuzzer: inferno_layout_test_fuzzer
Job Type: linux_asan_chrome_v8_arm
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x00000000
Crash State:
  webrtc::PeerConnection::GenerateMediaDescriptionOptions
  webrtc::PeerConnection::GetOptionsForAnswer
  webrtc::PeerConnection::CreateAnswer
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_v8_arm&range=496121:496160
Fixed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_v8_arm&range=496287:501540

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

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.

ClusterFuzz testcase 5703353370935296 is verified as fixed, so closing issue as verified.

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