Antwort: Re: pipeline memory consumption

Steffen.Roeber at hella.com Steffen.Roeber at hella.com
Mon Sep 12 04:30:01 PDT 2011


Hi,
thank you for the hint with the dot output. There I could see that the max 
buffer property of the the app sink has not been set correctly. After 
setting it correct all works fine.





Marco Ballesio/

( 
Gesendet von: 
gstreamer-devel-bounces+steffen.roeber=hella.com at lists.freedesktop.org
09.09.2011 15:08
Bitte antworten an
Discussion of the development of and with GStreamer 
<gstreamer-devel at lists.freedesktop.org>


An
Discussion of the development of and with GStreamer 
<gstreamer-devel at lists.freedesktop.org>
Kopie

Thema
Re: pipeline memory consumption






Hi,

there may be many reasons for the increased memory size, some of which
may even be fully legitimate depending on the system you're using and
what you're playing. Indeed there's always room for bugs ;). Some
questions below to help the community helping you ;).

On Thu, Sep 8, 2011 at 8:22 AM,  <Steffen.Roeber at hella.com> wrote:
>
> Hi,
> I'using a filesrc, decodebin2, ffmpegcolorspace, capsfilter and appsink
> pipeline which I use in pull mode. This means I pull the data of the 
appsink
> in a worker thread.

See here:

http://gstreamer.freedesktop.org/data/doc/gstreamer/head/gst-plugins-base-libs/html/gst-plugins-base-libs-appsink.html#gst-app-sink-pull-buffer


Are you consuming buffers fast enough? Are you properly unreffing them
when you're done?

> I also set the 'max-size-bytes' property of the  decodebin2 to 1000000 
and the
> gst_app_sink_set_max_buffers to 1. Anyhow after starting the pipeline, 
the
> memory consumption is rised up to more than 1gb, which decreases slowly
> while playing.

How are you measuring the memory allocated by the process? Might it be
that your system has an outrageous quantity of memory and that size is
used for filesystem caching?

> If I delete the pipeline all memory is freed. Who does take this memory?

You could be interested in dumping the pipeline topology on a dot
file: 
http://gstreamer.freedesktop.org/data/doc/gstreamer/head/gstreamer/html/gstreamer-GstInfo.html#GST-DEBUG-BIN-TO-DOT-FILE:CAPS


and verifying all the queues there are reasonably limited in length
and size. It would also be interesting to know which decoders you're
using and if any custom elements are used.

I hope this will help.

Regards

>
> Regards
>
> Hella Aglaia Mobile Vision GmbH
> Steffen Roeber
> Firmware & Tools
> Treskowstr. 14, D-13089 Berlin
> Amtsgericht Berlin-Charlottenburg HRB 66976 B
> Geschäftsführer: Kay Talmi
>
> Fon:  +49 30 200 04 29? 412
> Fax:  +49 30 200 04 29? 109
> Mail: Steffen.Roeber at hella.com
> URL: www.aglaia-gmbh.de
>
> URL: www.mobilevision.de
>
> Dieses Dokument ist vertraulich zu behandeln. Die Weitergabe sowie
> Vervielfältigung, Verwertung und Mitteilung seines Inhalts ist nur mit
> unserer ausdrücklichen Genehmigung gestattet. Alle Rechte vorbehalten,
> insbesondere für den Fall der Schutzrechtsanmeldung.
> This document has to be treated confidentially. Its contents are not to 
be
> pass ed on, duplicated, exploited or disclosed without our express
> permission. All rights reserved, especially the right to apply for
> protective rights.
> _______________________________________________
> gstreamer-devel mailing list
> gstreamer-devel at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel
>
>
_______________________________________________
gstreamer-devel mailing list
gstreamer-devel at lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/gstreamer-devel/attachments/20110912/8337310b/attachment.htm>


More information about the gstreamer-devel mailing list