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

[Måns Rullgård]

Bill May <wmay at cisco.com> writes:

> Hi,
>
> I'm trying out valgrind to make sure that there are no major memory
> leaks in my program.  I also tried the x264 program directly.
>
> 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.

> At the end, it finds 320K bytes in 20 blocks allocated in
> x264_mb_analyse_load_costs, which is the x264_malloc call for
> p_cost_mv[a->i_qp].
>
> Questions:
>
> 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?

> 2). It seems that p_cost_mv is never initialized to NULL; is this a good idea
>      that will work on all platforms ?

That's guaranteed by some standard.

-- 
Måns Rullgård
mru at inprovide.com

-- 
This is the x264-devel mailing-list
To unsubscribe, go to: http://developers.videolan.org/lists.html