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/+/101ae86567ba231c612af756e2bb5925a127ea30 (PC.setRemoteDescription: Use track-based callbacks over stream-based.).

If this is incorrect, please remove the owner and apply the Test-Predator-Wrong-CLs label.

My CL changed the way tracks and streams are handled by an RTCPeerConnection object in JavaScript. This looks irrelevant? Is this even running WebRTC?

(I couldn't see any repro html/javascript or figure out what the code running was, running the repro tool got stuck at reading some packet list, and the stack traces are unfamiliar to me)

ClusterFuzz has detected this issue as fixed in range 516797:516837.

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

Fuzzer: libFuzzer_mediasource_MP4_AACLC_AVC_pipeline_integration_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000000
Crash State:
  media::SourceBufferRangeByPts::GetBufferIndexAt
  media::SourceBufferRangeByPts::TruncateAt
  media::SourceBufferStream<media::SourceBufferRangeByPts>::RemoveInternal
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=508791:508824
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=516797:516837

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

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md 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 6352604539125760 is verified as fixed, so closing issue as verified.

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