[Bug 792407] New: GL context sharing fails in async loading mode.

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=792407

            Bug ID: 792407
           Summary: GL context sharing fails in async loading mode.
    Classification: Platform
           Product: GStreamer
           Version: 1.12.4
                OS: Windows
            Status: NEW
          Severity: normal
          Priority: Normal
         Component: gst-plugins-base
          Assignee: gstreamer-bugs at lists.freedesktop.org
          Reporter: petroskataras at gmail.com
        QA Contact: gstreamer-bugs at lists.freedesktop.org
     GNOME version: ---

Created attachment 366603
  --> https://bugzilla.gnome.org/attachment.cgi?id=366603&action=edit
async_load attempt

Hi,

I m currently testing the GstPlayer implementation I ve written for Cinder [1]
under Windows 10 [2] and I m hitting a snag.

The player so far has been battle tested on Linux which is my main development
platform but also ( albeit less ) on macOS. I would also like to make it
available under Windows but I m experiencing different behavior there.

More specifically the player works fine in sync loading mode after setting the
uri to load on playbin. e.g.

gst_element_set_state( pipeline, GST_STATE_PAUSED  );
gst_element_get_state( pipeline, nullptr, nullptr, GST_CLOCK_TIME_NONE );

but not in async mode:

gst_element_set_state( pipeline, GST_STATE_PAUSED  );

In the second case it throws :

ERROR from element convert : failed to share contexts through wglShareLists
0xaa
Debugging info : gstglbasefilter.c(393): gst_gl_base_filter_decide_allocation
():
/GstPlayBin:playbinsink/GstPlaySink:playsink/GstBin:vbin/GstBin:cinder-vbin/GstGLColorConvertElement:convert

Attached you can find an async_load attemt log and a successfull sync_load log
both with GST_DEBUG=*gl*:7

Any hints would be greatly appreciated.

Cheers,
Petros

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

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.