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.

Predator and CL could not provide any possible suspects.

Using Code Search for the file, "packet_buffer.cc" suspecting the below Cl might have caused this issue

Suspect CL: https://webrtc.googlesource.com/src.git/+/09133af36fba93691a22151765097c0bd581c1fa

Since author is OoO, assigning it to reviewer for further triage

brandtr@ -- Could you please look into this issue.

Thanks!

ClusterFuzz has detected this issue as fixed in range 580594:580602.

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

Fuzzer: libFuzzer_packet_buffer_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

Crash Type: Abrt
Crash Address: 0x053900000fa9
Crash State:
  Call<>
  webrtc::video_coding::RtpFrameObject::RtpFrameObject
  webrtc::video_coding::PacketBuffer::FindFrames
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=574469:574470
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=580594:580602

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

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

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