[FFmpeg-trac] #5139(undetermined:closed): memory leak when invalid data is found processing input
FFmpeg
trac at avcodec.org
Thu Jan 7 22:16:47 CET 2016
#5139: memory leak when invalid data is found processing input
-------------------------------------+-------------------------------------
Reporter: tsmith | Owner:
Type: defect | Status: closed
Priority: normal | Component:
Version: git-master | undetermined
Keywords: h264 leak | Resolution:
Blocking: | worksforme
Analyzed by developer: 0 | Blocked By:
| Reproduced by developer: 0
-------------------------------------+-------------------------------------
Changes (by cehoyos):
* status: new => closed
* resolution: => worksforme
Comment:
Please reopen if I miss something.
{{{
$ valgrind ffmpeg_g -f ivf -i test_case.ivf -f null -
==30399== Memcheck, a memory error detector
==30399== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al.
==30399== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright
info
==30399== Command: ffmpeg_g -f ivf -i test_case.ivf -f null -
==30399==
ffmpeg version N-77727-gf4c1a48 Copyright (c) 2000-2016 the FFmpeg
developers
built with gcc 4.7 (SUSE Linux)
configuration: --enable-gpl
libavutil 55. 12.100 / 55. 12.100
libavcodec 57. 22.100 / 57. 22.100
libavformat 57. 21.101 / 57. 21.101
libavdevice 57. 0.100 / 57. 0.100
libavfilter 6. 23.100 / 6. 23.100
libswscale 4. 0.100 / 4. 0.100
libswresample 2. 0.101 / 2. 0.101
libpostproc 54. 0.100 / 54. 0.100
st:0 has too large timebase, reducing
Truncating packet of size 1175257088 to 34917
[h264 @ 0xb721fa0] sps_id 32 out of range
[h264 @ 0xb721fa0] FMO not supported
[h264 @ 0xb721fa0] sps_id 32 out of range
Last message repeated 1 times
[h264 @ 0xb721fa0] Truncating likely oversized SPS
[h264 @ 0xb721fa0] sps_id 32 out of range
Last message repeated 1 times
[h264 @ 0xb721fa0] FMO not supported
[h264 @ 0xb721fa0] sps_id 32 out of range
[h264 @ 0xb721fa0] Truncating likely oversized SPS
[h264 @ 0xb721fa0] sps_id 32 out of range
Last message repeated 1 times
[h264 @ 0xb721fa0] Missing reference picture, default is 0
Last message repeated 2 times
[h264 @ 0xb721fa0] co located POCs unavailable
[h264 @ 0xb721fa0] error while decoding MB 86 3, bytestream -11
[h264 @ 0xb721fa0] non-existing SPS 0 referenced in buffering period
[h264 @ 0xb721fa0] number of reference frames (0+3) exceeds max (2;
probably corrupt input), discarding one
[h264 @ 0xb721fa0] concealing 258 DC, 258 AC, 258 MV errors in B frame
[ivf @ 0xb7187a0] decoding for stream 0 failed
Input #0, ivf, from 'test_case.ivf':
Duration: -404950:-11:-49.57, bitrate: N/A
Stream #0:0: Video: h264 (CAVLC 4:4:4) (V264 / 0x34363256), yuv444p,
1566x94, 278.66 tbr, 278.66 tbn, 557.33 tbc
Output #0, null, to 'pipe:':
Stream #0:0: Video: wrapped_avframe, yuv444p, 1566x94, q=2-31, 200
kb/s, 278.66 fps, 278.66 tbn, 278.66 tbc
Metadata:
encoder : Lavc57.22.100 wrapped_avframe
Stream mapping:
Stream #0:0 -> #0:0 (h264 (native) -> wrapped_avframe (native))
Error while opening decoder for input stream #0:0 : Invalid data found
when processing input
==30399==
==30399== HEAP SUMMARY:
==30399== in use at exit: 48 bytes in 1 blocks
==30399== total heap usage: 1,263 allocs, 1,262 frees, 4,224,114 bytes
allocated
==30399==
==30399== LEAK SUMMARY:
==30399== definitely lost: 0 bytes in 0 blocks
==30399== indirectly lost: 0 bytes in 0 blocks
==30399== possibly lost: 0 bytes in 0 blocks
==30399== still reachable: 48 bytes in 1 blocks
==30399== suppressed: 0 bytes in 0 blocks
==30399== Rerun with --leak-check=full to see details of leaked memory
==30399==
==30399== For counts of detected and suppressed errors, rerun with: -v
==30399== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 2 from 2)
}}}
--
Ticket URL: <https://trac.ffmpeg.org/ticket/5139#comment:3>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
More information about the FFmpeg-trac
mailing list