<br>>> After see that, I try run my full app with pipelines and everything<br>>> inside them. The memory leak continue growing and valgrind (already<br> >> with gst.supp file of the gstreamer git tree) show me some others<br> >> leaks, mainly on bus_* calls and plugin_* calls. is it too a normal<br> >> behavior? My app make many pipelines and finish them with<br> >> set_state(NULL) and with unref calls.<br> ><br> > It does not sound like normal behaviour, no.<br> ><br> > Hard to anything more specific without having a test case/program that<br> > reproduces the issue and the valgrind leak output. It could be a leak in<br> > your application or in some plugin or in GStreamer core.<br> <br>> Cheers<br> > -Tim<br clear="all"><br>Hi Tim,<br><br>Again, thanks for the good help!<br>I devel a simple example to show the leaks and attach it on email. the content is a .rar<br>because i put a simple image - necessary to example run (my appsrc read it and <br> push on pipeline) - the app.supp file; the valgrind output file generate after i run the <br> example per 16h; a README file to help on procedure; and the most important - the makefile.<br>The source is basically an appsrc to read image file and push it on pipeline periodically (1/fps).<br> The pipeline encode the images and generate many videos of 1s for me do something on appsink.<br>On example, i don't make nothing (just free the resources =). To don't stop the generation after <br>each EOS send to pipeline by appsrc, i put a loop on main (my app do that too). To a good stop of <br> app, just press Ctrl+C.<br><br>Some help is appreciated!<br><br>-- <br><div>Raul Holanda Cordeiro</div><div>Celular: +55 (85) 8863-6877</div><div>Celular: +55 (85) 8805-3592</div><div>Skype: raulhcordeiro</div><br>