[Bug 729088] xvimagesink: catch XWindows errors when destroying xwindow

[GStreamer (GNOME Bugzilla)]

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

Stirling Westrup <swestrup at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |swestrup at gmail.com

--- Comment #6 from Stirling Westrup <swestrup at gmail.com> ---
I just want to add that I'm also having problems with this bug. I have a
video-wall application that can have many xvimagesinks running at the same
time, right now if any one of them has a failure, the uncaught error ends up
aborting my entire program. Failure of one display out of 25 is annoying, but
not fatal. 

I would far rather just get a pipeline message of some kind, rather than an
abrupt termination.

However, looking at the xvimagesink code, I see its all Xlib based, and there
are known issues with trying to get error handling to work using Xlib in a
multi-threaded environment. All the recommendations are that in such
circumstances, you should recode the application to use xcb instead.

See here, for instance:
http://www.remlab.net/op/xlib.shtml

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