glimagesink: Only cache pool, don't manage it
authorNicolas Dufresne <nicolas.dufresne@collabora.com>
Thu, 5 Mar 2015 20:49:50 +0000 (15:49 -0500)
committerTim-Philipp Müller <tim@centricular.com>
Sat, 9 Dec 2017 19:31:56 +0000 (19:31 +0000)
commitbc92b41c7b939380415182087e9adaeb93b6b5e5
treeb87e553cfa96335faac6b263f5fc20b99063b350
parenteeab6e881f699a1cdfd7bb6405d04b63bae5be6a
glimagesink: Only cache pool, don't manage it

GLImage does not use any kind of internal pool. There was some
remaining code and comment stating that it was managing the
pool, and it was in fact setting the active state when doing
to ready state.

* Only create the pool if requested and in propose_allocation
* Cache the pool to avoid reallocation on spurious reconfigure
* Don't try to deactivate the pool (we don't own it)

https://bugzilla.gnome.org/show_bug.cgi?id=745705
ext/gl/gstglimagesink.c