Hi; On 10 June 2015 at 15:39, Lokesh Chakka <[email protected]> wrote: > hello, > > I am seeing my gtk application is frequently getting stuck in the following > stack
I bet that started happening because you updated GLib but not GTK+… > #0 0x00007fbc16d0d61a in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 > #1 0x00007fbc16d0d9a9 in g_mutex_unlock () from > /lib/x86_64-linux-gnu/libglib-2.0.so.0 > #2 0x00007fbc16ccbf91 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 > #3 0x00007fbc16ccc30a in g_main_loop_run () from > /lib/x86_64-linux-gnu/libglib-2.0.so.0 > #4 0x00007fbc17b4ffe5 in gtk_main () from > /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 > #5 0x00000000004057eb in main (argc=2, argv=0x7ffd67d2e188) at > MY_GTK_APPLICATION.c:100 > > > is this an error in Core GTK ? if so is there any fix ? No, it's very likely an issue in your application. Let me guess: you're initializing threading support, but you're not acquiring the lock before calling gtk_main(). You probably want to read this: https://www.bassi.io/articles/2014/08/27/gdk-and-threads/ If acquiring the GDK lock does not fix the issue, you'll have to provide more context. Ciao, Emmanuele. -- https://www.bassi.io [@] ebassi [@gmail.com] _______________________________________________ gtk-devel-list mailing list [email protected] https://mail.gnome.org/mailman/listinfo/gtk-devel-list
