[webkit-gtk] What supposed to hold the GDK in calls from WebKit/gtk/WebCoreSupport

Yehouda Harpaz yeh at lispworks.com
Sat Aug 20 03:00:18 PDT 2011


>  On Fri, Aug 19, 2011 at 9:27 AM, Yehouda Harpaz <yeh at lispworks.com> wrote:
>  >
>  >>  On Fri, Aug 19, 2011 at 5:22 AM, Yehouda Harpaz <yeh at lispworks.com> wrote:
>  >>  > We have problems integrating webkit-gtk into a multi0-threaded
>  >>  > application (Lisp IDE). We get "random" errors (i.e. not repeateable)
>  >>  > like the on in the first backtrace below. We suspect it is because of
>  >>  > calls to gdk functions without holding the gdk lock.
>  >>
>  >>  Are you using WebKitGTK+ on the main thread or some other thread?
>  >>  Typically all calls must be made on the main thread.
>  >
>  >
>  > We are calling WebKitGTK functions only on the main thread.
>  >
>  > But we are calling other GTK functions on other threads.
>  
>  http://blogs.operationaldynamics.com/andrew/software/gnome-desktop/gtk-thread-awareness

I read this and it didn't tell me anything that I don't already know,
and didn't answer the original question (what supposed to hold the GDK
lock in calls from WebKit/gtk/WebCoreSupport). 


More information about the webkit-gtk mailing list