Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.

Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/c220be7c001dbe68a36afc3e02838c510b0b3b0f (Fire RTCPeerConnection.onsignalingstatechange in the correct order.).

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.

ClusterFuzz has detected this issue as fixed in range 565967:565973.

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

Fuzzer: inferno_layout_test_unmodified
Job Type: linux_lsan_chrome_mp
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000088
Crash State:
  base::internal::WeakReference::is_valid
  get
  content::RTCPeerConnectionHandler::OnSignalingChange
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_lsan_chrome_mp&range=565290:565291
Fixed: https://clusterfuzz.com/revisions?job=linux_lsan_chrome_mp&range=565967:565973

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

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.