valgrind to track down memory issues (Re: Huge memory leak sometime after starting a pipeline)

[Vincent Génieux]

Hi all,

Le 2014-11-06 12:17, Tim Müller wrote :
> On Thu, 2014-11-06 at 11:33 +0100, Sergei Vorobyov wrote:
> 
> [...]
> 
>> Point is, to see "leaks", you need to stop your application, in which
>> case GStreamer produces thousands (miles) of messages of the kind:
> 
> As mentioned previously to you, valgrind is a suite of tools. The
> memcheck leak checker will only output a list of leaks at the end, that
> is true. There is also the 'massif' tool which allows you to track
> memory allocations as they build up over time,
> 
> [...]
> 

There are some valgrind macros that may be usefull to avoid stopping the 
application while doing a valgrind memcheck : VALGRIND_DO_LEAK_CHECK and 
VALGRIND_DO_CHANGED_LEAK_CHECK

-- 
vincent.