Automatically adding ccs based on suspected regression changelists:

Actually input packets into the PacketBuffer. by philipel@webrtc.org - https://webrtc.googlesource.com/src/+/32134470cacefecc27d59a0086aed71f9663404b

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label.

Since philipel@ is OoO, assigning it to the reviewer for further triage.

aleloi@ Could you please look into this issue.

 Issue 865308  has been merged into this issue.

ClusterFuzz has detected this issue as fixed in range 580597:580599.

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

Fuzzer: libFuzzer_packet_buffer_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: Abrt
Crash Address: 0x053900006063
Crash State:
  rtc::webrtc_checks_impl::FatalLog
  webrtc::video_coding::RtpFrameObject::RtpFrameObject
  webrtc::video_coding::PacketBuffer::FindFrames
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=574469:574470
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=580597:580599

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

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

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