GNOME Bugzilla – Bug 635065
gtk_main_quit works not properly when app is closed over win32 taskbar
Last modified: 2011-06-10 08:14:13 UTC
Created attachment 174669 [details] short demonstration of this I noticed that my application causes a sigfault in gtk_main_quit when it was closed over the win32 taskbar menu. I wrote a small test-application to verify this. This application causes glib warnings when the win32 Taskbar menu is opened: (test_statusbar.exe:5568): GLib-WARNING **: g_main_context_prepare() called recursively from within a source's check() or prepare() member. (test_statusbar.exe:5568): GLib-WARNING **: g_main_context_check() called recursively from within a source's check() or prepare() member. When the test-application is closed over the taskbar menu, functions which were added over gtk_timeout_add are triggered after gtk_main_quit has been called. All other methods to close the application are working well: (ALT+F4), close with application button, close with win32 frame, close with taskmanager. (test_statusbar.exe:4808): GLib-WARNING **: g_main_context_check() called recursively from within a source' (test_statusbar.exe:4808): GLib-WARNING **: g_main_context_prepare() called recursively from within a sourc When I close the test-application over the taskbar-menu, you can see that the idle_add_fuction causes warnings AFTER gtk_main_quit gas been called. console output of test-app: (test_statusbar.exe:4808): GLib-WARNING **: g_main_context_check() called recursively from within a source' I ran through my_exit!! This is after gtk_main_quit!! (test_statusbar.exe:4808): GLib-GObject-WARNING **: invalid uninstantiatable type `<invalid>' in cast to `G (test_statusbar.exe:4808): Gtk-CRITICAL **: gtk_label_set_text: assertion `GTK_IS_LABEL (label)' failed Version: glib_2.24.0-2_win32 glib-dev_2.24.0-2_win32 pkg-config_0.23-3_win32 pkg-config-dev_0.23-3_win32 atk_1.30.0-1_win32 atk-dev_1.30.0-1_win32 pango_1.28.0-1_win32 pango-dev_1.28.0-1_win32 cairo_1.8.10-3_win32 cairo-dev_1.8.10-3_win32 fontconfig_2.8.0-2_win32 fontconfig-dev_2.8.0-2_win32 expat_2.0.1-1_win32 expat-dev_2.0.1-1_win32 freetype_2.3.12-1_win32 freetype-dev_2.3.12-1_win32 libpng_1.4.0-1_win32 libpng-dev_1.4.0-1_win32 zlib_1.2.4-1_win32 zlib-dev_1.2.4-1_win32 gtk+_2.20.0-1_win32 gtk+-dev_2.20.0-1_win32
what the heck is a "sigfault"?
Sorry, I mean segfault -> segmentation fault.
Yeah, this is #552041. There's a patch there, but it's in need of review... *** This bug has been marked as a duplicate of bug 552041 ***