<html> <head> <base href="https://bugzilla.gnome.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Sometimes tooltip_popup_timeout() in gtk/gtktooltip.c causes crash after closing a window" href="https://bugzilla.gnome.org/show_bug.cgi?id=784319#c11">Comment # 11</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Sometimes tooltip_popup_timeout() in gtk/gtktooltip.c causes crash after closing a window" href="https://bugzilla.gnome.org/show_bug.cgi?id=784319">bug 784319</a> from <a href="page.cgi?id=describeuser.html&login=ofourdan%40redhat.com" title="Olivier Fourdan <ofourdan@redhat.com>"> Olivier Fourdan</a> <pre>I tried to reproduce this with a simple gtk+ program, but failed to reproduce, so it could be /something/ that firefox does. >From what I can see, we get an additional motion event for the gdk window which is about to be destroyed, so we end up in gtk_tooltip_handle_event_internal() with the event window being from the widget that has just been unrealized, so it will start a gtk_tooltip_start_delay() that will end up crashing. Obviously, <a href="attachment.cgi?id=354667&action=diff" name="attach_354667" title="A patch to avoid the crash">attachment 354667</a> <a href="attachment.cgi?id=354667&action=edit" title="A patch to avoid the crash">[details]</a> <a href='review?bug=784319&attachment=354667'>[review]</a> will avoid the crash, but I cannot really tell whether or not this is correct unless I understand what mechanism leads to this issue (i.e. I have the feeling that the patch is hiding the problem more than solving it, and I'm not even sure the problem is in gtk+ rather than firefox in the first place).</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> </ul> </body> </html>