Direct-leak in update_frag_index |
||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5973513158262784 Fuzzer: libFuzzer_media_pipeline_integration_fuzzer Fuzz target binary: media_pipeline_integration_fuzzer Job Type: libfuzzer_chrome_asan Platform Id: linux Crash Type: Direct-leak Crash Address: Crash State: update_frag_index mov_read_moof mov_read_default Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=617278:617279 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5973513158262784 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for instructions to reproduce this bug locally.
,
Dec 18
Automatically adding ccs based on OWNERS file / target commit history. If this is incorrect, please add ClusterFuzz-Wrong label.
,
Dec 18
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/third_party/ffmpeg/+/8b857829e499caea0ac4fbd284115aa9347e2e42 (lavf/mov: ensure only one tkhd per trak). 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.
,
Dec 18
Good job ClusterFuzz. That CL bails on the populating of an allocated array due to invalid file structure.
if (c->fc->streams[i]->id < 0)
return AVERROR_INVALIDDATA;
We should free the frag_stream_info prior to returning.
|
||||
►
Sign in to add a comment |
||||
Comment 1 by ClusterFuzz
, Dec 18Labels: Test-Predator-Auto-Components