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 565971:565973.

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

Fuzzer: phoglund_webrtc_peerconnection
Job Type: linux_ubsan_vptr_chrome
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000000
Crash State:
  content::RTCPeerConnectionHandler::OnSignalingChange
  content::RTCPeerConnectionHandler::SetLocalDescriptionRequest::OnSuccessOnMainTh
  base::debug::TaskAnnotator::RunTask
  
Sanitizer: undefined (UBSAN)

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

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

Additional requirements: Requires HTTP

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.