GNOME Bugzilla – Bug 589127
gsttask leaks the pool
Last modified: 2009-07-20 16:04:45 UTC
GstTask takes a ref to a taskpool when creating a thread but does not release that ref when the pool does not provide a pointer for joining the thread.
Created attachment 138819 [details] [review] possible fix Fixes the leak.
Is this a regression? How comfortable are you putting it in during freeze?
it's a regression because of the GstTask work for 0.10.24. I'm pretty sure the patch is correct.
OK, push the commit
commit ffca244c262743ddf99fd06f66df979ba556f499 Author: Wim Taymans <wim.taymans@collabora.co.uk> Date: Mon Jul 20 18:03:21 2009 +0200 tests: make sure the tasks are joined Call _clean_all() on the task to make sure everything is joined and stopped. See #589127 commit a78199ae5e48cabec1ed5c733e84debfc55578ca Author: Wim Taymans <wim.taymans@collabora.co.uk> Date: Mon Jul 20 15:44:36 2009 +0200 task: fix taskpool leak GstTaks does not always unref the taskpool it was created from because it depends on when the pool provided an ID for joining the task. Rework some code so that we always unref the pool and optionally join when the pool provided an id. Fixes #589127