Proper pipeline destruction in GStreamer 1.2.3

Sebastian Dröge sebastian at
Wed Feb 26 11:33:37 PST 2014

On Mi, 2014-02-26 at 09:29 -0800, Frank M. wrote:
> Hello,
> I launch the following pipeline description:
> appsrc do-timestamp=true name=source !
> multipart/x-mixed-replace,boundary=--myboundary !
> multifdsink name=sink sync=false units-max=30 units-soft-max=6
> recover-policy=latest sync-method=latest 
> When I destroy the pipeline by setting it's state to NULL and unref'ing the
> pointer to it the CPU usage of my 
> process goes to 100% which wasn't the case in older GStreamer versions. Was
> there any fundamantal change in how pipelines should be destroyed in
> GStreamer 1.2.3 ? 

There wasn't and if there is such a change it would be a bug. Please
check with a debugger or from the debug logs what is happening there, or
file a bug with a testcase at

Sebastian Dröge, Centricular Ltd -
Expertise, Straight from the Source
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 949 bytes
Desc: This is a digitally signed message part
URL: <>

More information about the gstreamer-devel mailing list