Memory leaks with partial pipeline destruction

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view

Memory leaks with partial pipeline destruction

Thornton, Keith


I have a relatively complicated pipeline with a tee followed by amongst others a streaming branch, a recording branch and a live image branch. When I am not recording, I dismantle the recording branch by setting a pad probe on the sink of the first element after the tee. I then send EOS down the pipeline, I unlink the elements, set theier states to NULL and remove them from the pipeline. I am noticing that these elements still have ref_counts > 1 (e.g. 12) When I re-add / re-link the elements for the next recording I observe a large memory leak. Does anyone know what it is I am not doing correctly while dismantling these partial pipeline branches?


gstreamer-devel mailing list
[hidden email]