[Bug 752379] gl: deadlock when destroying GstGLContext from within a windows event callback

[GStreamer (GNOME Bugzilla)]

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

--- Comment #2 from Xavier Claessens <xclaesse at gmail.com> ---
I quickly checked the d3dvideosink code and it seems the window there creates
its own thread to handle messages. I'm wondering if it's suffering from the
same bug or not, will test.

It seems pretty obvious for a stop button to set pipeline to NULL, that's the
most common use-case, so we should try harder to make it work. Everybody is
going to fall in that trap otherwise, IMO.

Note that I'm far from a win32 expert, so it's possible my analysis of the
problem is wrong. All I know is that my app (sadly proprietary, I'll try to
make simple test case) hang in DestroyWindow when I set pipeline to NULL in the
mouse click callback.

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