not sure if this is a GStreamer bug or some kind of GPU driver madness so
posting here before opening a bug.
I m currently trying the gst-based video player I have written for Cinder
 on Ubuntu 18.04 ( stock GStreamer 1.14.1 ) with an NVIDIA GPU and driver
390.87 and I m getting consistent assertion failures on GstGLDisplay when
destroying a player and creating a new one.
Same codebase has been working fine on Ubuntu 16.04 ( albeit not tested with
the 390 driver ) so not sure where the problem lies exactly.
Attached a log output of the failure configured with GST_DEBUG=*gl*:7.
Thanks a lot for your reply - This turned out to be a bug on my side that
would only manifest when having multiple players running in parallel. Sorry
for the false alarm.
That said and in the process of testing more aggressively the GL path the
last couple of days, I m experiencing a memory leak when constructing and
deconstructing multiple players that only happens when using GL elements in
the pipeline ( i.e the player has also support for the traditional appsink -
cpu path where I create the texture on my own from system memory without
using gst-gl elements and in this case the leak is not present. )
To make it even more interesting the leak doesn't seem to show when running
the app through Valgrind but I will post a separate topic for this.