[x264-devel] Re: Memory leak detected using Valgrind

[Bill May]

Måns Rullgård wrote:
> Bill May <wmay at cisco.com> writes:
>>Valgrind first finds over 30000 occurrances of "Use of uninitialized
>>value of size 8" within x264 - no backtrace.
> 
> 
> Without a backtrace, it's very difficult to tell where it came from.

I can't figure a way to backtrace - it's most likely in the nasm code.
I tried compiling with out nasm, but it didn't compile - looked for
altivec.h.


>>1). Do we care ?
> 
> 
> Well, it's only a small amount, so it's no big deal.  Ideally, it
> should be freed, but I can't come up with a good way off the top of my
> head.  Suggestions?

Make it an external and free it in x264_encoder_close.  Or static to that
file with a function that clears the memory.

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: x264.diffs
Url: http://mailman.videolan.org/pipermail/x264-devel/attachments/20050406/cb08c24c/attachment.txt