GST_IS_GL_DISPLAY assertion failure - Ubuntu 18.04 - NVIDIA

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

GST_IS_GL_DISPLAY assertion failure - Ubuntu 18.04 - NVIDIA

petros
Hi,

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
[1] 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.

Any pointers would be greatly appreciated.

Best,
Petros

[1]
https://github.com/cinder/Cinder/blob/master/src/cinder/linux/GstPlayer.cpp

gst_log.txt
<http://gstreamer-devel.966125.n4.nabble.com/file/t377246/gst_log.txt>  



--
Sent from: http://gstreamer-devel.966125.n4.nabble.com/
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel
Reply | Threaded
Open this post in threaded view
|

Re: GST_IS_GL_DISPLAY assertion failure - Ubuntu 18.04 - NVIDIA

petros
Something to note that at least to me seems strange from GStreamer's side is
that even *after* setting the pipeline to NULL the GstGLDisplay has still a
refcount > 1.

I would expect that at that point ( i.e after the pipeline deconstruction )
the refcount should be equal to 1 ( as it happens with GstGLContext ) but
this is not the case.



--
Sent from: http://gstreamer-devel.966125.n4.nabble.com/
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel
Reply | Threaded
Open this post in threaded view
|

Re: GST_IS_GL_DISPLAY assertion failure - Ubuntu 18.04 - NVIDIA

Matthew Waters
In reply to this post by petros
I'm not sure of this off the top of my head.

You can try getting a backtrace of the warnings and see where that
leads?  Also running the application with asan or valgrind might be useful.

Cheers
-Matt

On 7/10/18 8:10 pm, petros wrote:

> Hi,
>
> 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
> [1] 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.
>
> Any pointers would be greatly appreciated.
>
> Best,
> Petros
>
> [1]
> https://github.com/cinder/Cinder/blob/master/src/cinder/linux/GstPlayer.cpp
>
> gst_log.txt
> <http://gstreamer-devel.966125.n4.nabble.com/file/t377246/gst_log.txt>  
>
>
>
> --
> Sent from: http://gstreamer-devel.966125.n4.nabble.com/
> _______________________________________________
> gstreamer-devel mailing list
> [hidden email]
> https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

signature.asc (499 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: GST_IS_GL_DISPLAY assertion failure - Ubuntu 18.04 - NVIDIA

petros
Hi Matt,

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.

Thanks again.
Petros



--
Sent from: http://gstreamer-devel.966125.n4.nabble.com/
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel