GNOME Bugzilla – Bug 764993
libs: fix deleting a GstVaapiCodedBufferPool object
Last modified: 2016-04-29 08:43:26 UTC
Created attachment 325859 [details] [review] patch Call gst_vaapi_video_pool_finalize() in coded_buffer_pool_finalize(). Otherwise it is not called when the pool is destroyed and all objects referenced by the GstVaapiVideoPool are never released.
Comment on attachment 325859 [details] [review] patch Great catch! Being just code wise, I would like to know if it is possible to stick to the gobject-like code style. I mean, to keep someware the parent_finalize and call it from the class structure. Though this is the most direct solution.
Comment on attachment 325859 [details] [review] patch I checked and it is not possible to save the parents finalize pointer as it is. Hence the patch is correct.
Comment on attachment 325859 [details] [review] patch commit 1e32d62c1e27e4df5d127c30fd3b6084e2db8483 Author: Michael Olbrich <m.olbrich@pengutronix.de> Date: Wed Apr 13 14:09:00 2016 +0200 libs: fix deleting a GstVaapiCodedBufferPool object Call gst_vaapi_video_pool_finalize() in coded_buffer_pool_finalize(). Otherwise it is not called when the pool is destroyed and all objects referenced by the GstVaapiVideoPool are never released. https://bugzilla.gnome.org/show_bug.cgi?id=764993