After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 746701 - glimagesink: cannot set window handle to 0
glimagesink: cannot set window handle to 0
Status: RESOLVED OBSOLETE
Product: GStreamer
Classification: Platform
Component: gst-plugins-base
unspecified
Other Linux
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2015-03-24 18:41 UTC by Xavier Claessens
Modified: 2018-11-03 11:36 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Xavier Claessens 2015-03-24 18:41:11 UTC
When I set glimagesink's window-handle to 0, I get that critical:

** (lt-scout-client-gtk:25380): CRITICAL **: gst_gl_window_set_window_handle: assertion 'handle != 0' failed

But gst_video_overlay_set_window_handle()'s doc says this:
"Passing 0 as the handle will tell the overlay to stop using that window and create an internal one."

In my case I'm on android, since it cannot create a new window there, I guess the sink has 2 options: drop buffers or block the streaming thread (equivalent of PAUSED, right?) until it get a new window handle. On android when switching app the SurfaceView is destroyed so in that case it sets the window-handle to 0 and I think it makes sense to pause the stream.
Comment 1 Julien Isorce 2017-09-06 13:27:49 UTC
The doc seems correct as you can pass 0 to ximagesink and xvimagesink at least.

Have you try to just remove the check "g_return_if_fail (handle != 0);" ? 
I am saying that because looking at gstglwindow_x11.c and gstglwindow_android_egl.c it looks like it should work.
Comment 2 GStreamer system administrator 2018-11-03 11:36:16 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/gstreamer/gst-plugins-base/issues/175.