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 adding ccs based on OWNERS file / target commit history.

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

Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/third_party/ffmpeg/+/db2a7c947ec28b0a04a4e5193c9b0d33de823fbb (avcodec/avcodec.h: Add encryption info side data.).

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.

Since I'm working on patches for FFmpeg (not related to Chrome), I've updated one of them to fix this.

http://ffmpeg.org/pipermail/ffmpeg-devel/2018-May/230514.html

Is there a desire to send a CL to fix the Chrome tree as well, or wait until that patch is merged upstream?

ClusterFuzz has detected this issue as fixed in range 561996:562010.

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

Fuzzer: libFuzzer_media_pipeline_integration_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000038
Crash State:
  av_encryption_info_clone
  base::CreateThread
  base::internal::SchedulerWorker::Start
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=560371:560389
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=561996:562010

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

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

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