[Ffmpeg-devel] Possible memory leak when writing ASF files (asf, wmv, etc...)
Sun Mar 11 22:26:20 CET 2007
On Sun, Mar 11, 2007 at 08:51:56PM +0200, Stas Oskin wrote:
> When creating a new ASF/WMV file, valgrind reports the following
> warning on a first write:
> ==18643== Syscall param write(buf) points to uninitialised byte(s)
> ==18643== at 0x30AE1B933F: (within /lib64/tls/libc-2.3.4.so)
> ==18643== by 0x4A346FF: file_write (file.c:62)
> ==18643== by 0x4A32C0E: url_write (avio.c:117)
> ==18643== by 0x4A33D3C: url_write_packet (aviobuf.c:478)
> ==18643== by 0x4A32F66: flush_buffer (aviobuf.c:68)
> ==18643== by 0x4A330FA: put_flush_packet (aviobuf.c:110)
> ==18643== by 0x4A470A0: flush_packet (asf-enc.c:602)
> ==18643== by 0x4A473ED: put_frame (asf-enc.c:712)
> ==18643== by 0x4A47582: asf_write_packet (asf-enc.c:740)
> ==18643== by 0x4A2F6CD: av_write_frame (utils.c:2197)
> All the subsequent writes are ok. I traced the program, and the buv
> value is always equal to "\202".
> Any idea what is happening?
if any code in the asf muxer did write uninitalized data then we would
have noticed this in the regression tests already
so i will leave this to you/a volunteer to investigate further
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Opposition brings concord. Out of discord comes the fairest harmony.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: not available
More information about the ffmpeg-devel