Re: [Gnash-dev] "GdkWindow unexpectedly destroyed"

[strk]

GdkWindow unexpectedly destroyed happens when a DESTROY event
is sent by X before a DELETE one is sent. At least this is
what it seems by hooking on both events.

Also, it seems that if we don'g call gtk_main_quit on that
event we don't get a segfault in plugin. No idea why yet.

--strk;

On Thu, Feb 12, 2009 at 01:48:56PM -0800, John Gilmore wrote:
> Browsing the FlowPlayer.org site, and a few others, using the trunk
> gnash, I got these messages in a terminal:
> 
> (gtk-gnash:12345): Gdk-WARNING **: GdkWindow 0x7200023 unexpectedly destroyed
> 
> (gtk-gnash:12345): Gdk-WARNING **: GdkWindow 0x7200003 unexpectedly destroyed
> The program 'gtk-gnash' received an X Window System error.
> This probably reflects a bug in the program.
> The error was 'BadWindow (invalid Window parameter)'.
>   (Details: serial 179 error_code 3 request_code 18 minor_code 0)
>   (Note to programmers: normally, X errors are reported asynchronously;
>    that is, you will receive the error a while after causing it.
>    To debug your program, run it with the --sync command line
>    option to change this behavior. You can then get a meaningful
>    backtrace from your debugger if you break on the gdk_x_error() function.)
> 
> Unfortunately I can't point you to the site that generated them.
> Are they usual and expected, or are they something I should spend time
> chasing down?
> 
>       John
> 
> 
> _______________________________________________
> Gnash-dev mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/gnash-dev

-- 

 Free GIS & Flash consultant/developer      ()  ASCII Ribbon Campaign
 http://foo.keybit.net/~strk/services.html  /\  Keep it simple!