Debugging GStreamer : refcounting

[Thomas Scheuermann]

Am 15.07.2013 11:46, schrieb Tim-Philipp Müller:
>> I use here gstreamer-sdk with gstreamer-0.10 on a 32-bit debian wheezy.
>> I want to debug the reference counters and found the debug variable:
>> GST_DEBUG=GST_REFCOUNTING:5
>> but I can't interpret the output.
>> Is there a way to see if there are any references which need to be
>> unrefed but which are not?
>>
>> In the end we are looking here for memory problems with gstreamer,
>> because it crashes after it has reached 3GB memory.
> if you're on Linux, I'd recommend the valgrind suite of tools.
>
>   $ G_SLICE=always-malloc valgrind --leak-check=yes yourapplication
>
> (you can also pass suppression files from the GStreamer common module so
> it doesn't report one-time allocations in GObject and GStreamer and
> things like that, cuts down the noise a little).
How can I do this?
Is there a documentation about this?
If I use valgrind the video doesn't play correctly at all. We have the
situation here that we only have streaming videos which we have to decode.
> Warning: Malformed stack trace detected.
> Then there's also the valgrind tool "massif", with which you can track
> where what gets allocated over time. This is useful if it doesn't leak,
> but just builds up somewhere. Again, use G_SLICE=always-malloc.
with massif I only get 'Warning: Malformed stack trace detected.'
> Cheers
>   -Tim
>
Regards,

Thomas


DISCLAIMER: Unless indicated otherwise, the information contained in this message is privileged and confidential, and is intended only for the use of the addressee(s) named above and others who have been specifically authorized to receive it. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this message and/or attachments is strictly prohibited. The company accepts no liability for any damage caused by any virus transmitted by this email. Furthermore, the company does not warrant a proper and complete transmission of this information, nor does it accept liability for any delays. If you have received this message in error, please contact the sender and delete the message. Thank you.