Re: gtk application getting stuck in g_mutex_unlock


thanks for your quick response.
As per your suggestion, I added gdk threads init/enter/leave. Still I am facing the same problem.

Regarding the context,

I am working on a proprietary software which analyses network traffic and plots that info as a graph. you can visualize this as similar to system monitor.

This software takes configuration from end user. For configuring, we are using spin buttons, combo boxes, buttons, tool bar, pan, notebook, file chooser, scrolled windows etc.

For plotting the graph, I am using color buttons, cairo graphics etc.

please let me know if I have to give any more related to context.

Thanks & Regards
Lokesh Chakka,
Mobile: 9731023458

On Wed, Jun 10, 2015 at 8:17 PM, Emmanuele Bassi <ebassi gmail com> wrote:

On 10 June 2015 at 15:39, Lokesh Chakka <lvenkatakumarchakka gmail com> 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/
> #1  0x00007fbc16d0d9a9 in g_mutex_unlock () from
> /lib/x86_64-linux-gnu/
> #2  0x00007fbc16ccbf91 in ?? () from /lib/x86_64-linux-gnu/
> #3  0x00007fbc16ccc30a in g_main_loop_run () from
> /lib/x86_64-linux-gnu/
> #4  0x00007fbc17b4ffe5 in gtk_main () from
> /usr/lib/x86_64-linux-gnu/
> #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 []

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]