GNOME Bugzilla – Bug 141416
leak in entrygthread scheduler
Last modified: 2004-12-22 21:47:04 UTC
The cothread context isn't freed by the entrygthread scheduler when the object is destroyed
Created attachment 27213 [details] [review] Destroy the cothread context in the dispose method
cothread contexts are supposed to be freed by calling the (misnamed) gst_scheduler_reset function, which would make this patch unnecessary. Not calling this function before freeing a scheduler sounds like a bug to me. The other schedulers don't free their context in a dispose function either.
Who is supposed to call this gst_scheduler_reset() function? It doesn't work with 0.8.1 at least. Would it be this part in gstpipeline.c: /* FIXME: calling gst_scheduler_reset() here is bad, since we * might not be in cothread 0 */ #if 0 if (GST_ELEMENT_SCHED (element)) { gst_scheduler_reset (GST_ELEMENT_SCHED (element)); } #endif And basicgthread leaks too. Opt doesn't leak for me, but its compiled without cothreads.
should be fixed in CVS (I hope)