Re: gtk application getting stuck in g_mutex_unlock
- Date: Wed, 10 Jun 2015 15:47:31 +0100
- From: Emmanuele Bassi <ebassi@xxxxxxxxx>
- Subject: Re: gtk application getting stuck in g_mutex_unlock
On 10 June 2015 at 15:39, Lokesh Chakka <lvenkatakumarchakka@xxxxxxxxx> wrote:
> I am seeing my gtk application is frequently getting stuck in the following
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
> #2 0x00007fbc16ccbf91 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
> #3 0x00007fbc16ccc30a in g_main_loop_run () from
> #4 0x00007fbc17b4ffe5 in gtk_main () from
> #5 0x00000000004057eb in main (argc=2, argv=0x7ffd67d2e188) at
> 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:
If acquiring the GDK lock does not fix the issue, you'll have to
provide more context.
[@] ebassi [@gmail.com]
gtk-devel-list mailing list