Automatically adding ccs based on OWNERS file / target commit history.

If this is incorrect, please add ClusterFuzz-Wrong label.

Automatically adding ccs based on suspected regression changelists:

Change RTPVideoTypeHeader to absl::variant and move RTPVideoHeader into its own h/cc file. by philipel@webrtc.org - https://webrtc.googlesource.com/src/+/1a4746a56370c6a1643a420184a5de047feb878f

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, "internal/raw_logging.cc" suspecting the below Cl might have caused this issue

Suspect CL: https://chromium.googlesource.com/chromium/src/+/f4f0f0e2af28098ac58f8548b13d1a1f46d7c846

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

Thanks!

I don't think https://chromium.googlesource.com/chromium/src/+/f4f0f0e2af28098ac58f8548b13d1a1f46d7c846 is the culprit.

It is more likely that https://webrtc-review.googlesource.com/c/src/+/87561 triggered this error.

Assigning to philipel@ for triaging.

ClusterFuzz has detected this issue as fixed in range 591176:591178.

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

Fuzzer: libFuzzer_rtp_frame_reference_finder_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

Crash Type: Abrt
Crash Address: 0x053900006d36
Crash State:
  RawLogVA
  absl::raw_logging_internal::RawLog
  absl::variant_internal::ThrowBadVariantAccess
  
Sanitizer: memory (MSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=574465:574473
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=591176:591178

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

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

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