<div class="gmail_quote">2010/3/2 Jan Schmidt <<a href="mailto:thaytan@noraisin.net">thaytan@noraisin.net</a>> <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> You should ensure in Application A, that you call XSync, or gdk_display_sync (gdk_display_get_default()) - otherwise by the time Application B accesses the Window XID, it might not yet actually exist in the X server, leading to the crash. </blockquote><div> I'm working on the same kind of problem but I've noticed that Application B will sometimes create a window for a split second, i'm guessing right before the set_xwindow_id call. Can this be avoided? I know this API has changed recently. I'm using Ubunty 8.04, with glib1.2.10 and the following gstreamer releases installed: gstreamer 0.10.25 gstreamer-plugin-base 0.10.25 gst-plugin-good 0.10.17 gst-plugin-bad 0.10.17 gst-plugin-ugly 0.10.13 gst-ffmpeg 0.10.10.9 Here's my code: bool handleBusMsg(GstMessage *message) { if (!gst_structure_has_name(message->structure, "prepare-xwindow-id")) return false; gdk_threads_enter(); gst_x_overlay_set_xwindow_id(GST_X_OVERLAY(GST_MESSAGE_SRC(message)), getXWindow()); gdk_threads_leave(); } Thanks, Tristan </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> - Jan. <div class="im"> On Sat, 2010-02-27 at 17:23 -0800, yiliang wrote: </div><div class="im">> Hi, > > I have 2 applications. One application (application A) creates a window, and > sends the window ID to another application (application B). application B > has a gstreamer video pipeline that uses xvimagesink to display the video as > overlay in the window using the window ID provided by application A. I am > sorry if it sounds a little confusing. This is to separate UI from pipeline. > > Following function is used to configure xvimagesink with window ID: > > gst_x_overlay_set_xwindow_id(GST_X_OVERLAY(xvimagesink), winId); > > Most of time it works fine, but sometimes I encounter the following problem, > and the application B is terminated: > > X Error of failed request: BadWindow (invalid Window parameter) > Major opcode of failed request: 3 (X_GetWindowAttributes) > Resource id in failed request: 0x400016f > Serial number of failed request: 32 > Current serial number in output stream: 33 > > After some debugging, I found the error was generated in function > gst_xvimagesink_set_xwindow_id() when it called the following function: > > XGetWindowAttributes > > Could anyone give some hint how to fix this problem? > > Thanks, > Yiliang > -- </div>Jan Schmidt <<a href="mailto:thaytan@noraisin.net">thaytan@noraisin.net</a>> <div><div></div><div class="h5"> ------------------------------------------------------------------------------ Download Intel&#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. <a href="http://p.sf.net/sfu/intel-sw-dev" target="_blank">http://p.sf.net/sfu/intel-sw-dev</a> _______________________________________________ gstreamer-devel mailing list <a href="mailto:gstreamer-devel@lists.sourceforge.net">gstreamer-devel@lists.sourceforge.net</a> <a href="https://lists.sourceforge.net/lists/listinfo/gstreamer-devel" target="_blank">https://lists.sourceforge.net/lists/listinfo/gstreamer-devel</a> </div></div></blockquote></div> -- Tristan Matthews email: <a href="mailto:tristan@sat.qc.ca">tristan@sat.qc.ca</a> web: <a href="http://tristanswork.blogspot.com">http://tristanswork.blogspot.com</a>