GNOME Bugzilla – Bug 700513
Random/hardly reproducible crash in glib
Last modified: 2018-05-24 15:20:32 UTC
I'm usign pyGtk to interact with GTK+ under both Linux and Windows. Under windows used builds from latest win32 bundle (20120208) from http://gtk.org/download/win32.php On one of computer application get crashed quite often with crash inside libglib. It has that crash on previous version (2.28.1.0), and after upgrade to latest one it still has crash. Crash information from windows: Fault Module Name: libglib-2.0-0.dll Fault Module Version: 2.28.8.0 Fault Module Timestamp: 4e253544 Exception Code: 40000015 Exception Offset: 0004c2d8 Googling with "Exception Offset: 0004c2d8" gives several questions about that crash in other softwares, that also uses gtk: Deluge, zenmap. I can't find any useful information about way I can debug / workaround that bug. Since it on windows, and not on my build machine, i can't even install any debugger to try to find stack trace. Installing of all latest OS updates doesn't make any sense. OS: Win7 x64, CPU: Intel Core i5, memory: 4Gb, videocard: nvidia Any way I can help to find sqrt(problem) ?
If '0004c2d8' if offset from start of library base addres, it seems that crash in g_assertion_message function. on stdout/stderr no message printed... any way to catch that message any other way?
Hi Anton, Can you let us know what you were doing that lead to your crash? With blessings, thank you.
Oh! Forget about that filed bug. I have got that assertions, by catching all stdout/stderr into logs. lib\graph\base.py:333: GtkWarning: gdk_drawable_copy_to_image: assertion `src_y >= 0' failed^M lib\graph\base.py:334: GtkWarning: gdk_drawable_copy_to_image: assertion `src_y >= 0' failed^M gui.py:376: GtkWarning: inner_clipboard_window_procedure: assertion `success' failed It looks to happens only in multithreaded setup. I have just hardly stick absolutely all GTK operations to single thread, and then it working fine. Using locking to access from different threads NOT working, only access from single thread works.
Hi Anton, Unfortunately at the current state of GTK+ it is not possible for multithreaded GTK+ apps to work on Windows in many cases, due to the fact that Windows has a number of implicit locks that are done internally, as we enter the GUI subsystem. As noted in README.win32 in GTK+, it is mentioned under the sub-title: "Multi-threaded use of GTK+ on Win32" Sorry, as possible solutions need to be investigated for this due to the way GTK+ is structured code-wise. With blessings!
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/glib/issues/704.