[webkit-dev] segfault when having multiple webkit instances (got backtrace)

[Maciej Stachowiak]

On Oct 6, 2008, at 1:24 AM, Luka Napotnik wrote:

> Hello.
>
> Thanks for the quick reply. It seems that locking the GDK subsystem
> before every call to WebKit is not enough. Can this be a problem with
> the way how WebKit manages memory? Is there a locking function for  
> that?

There are all sorts of things WebKit does that are not threadsafe, and  
I do not believe any amount of locking by a client of WebKit can fix  
them all. Even holding a global mutex around all WebKit entry points  
will not do it, since WebKit schedules some work itself to be done  
asynchronously.

Regards,
Maciej

>
>
> Greets,
> Luka
>
> Dne 06.10.2008 (pon) ob 01:10 -0700 je Maciej Stachowiak zapisal(a):
>> On Oct 6, 2008, at 12:50 AM, Luka Napotnik wrote:
>>
>>> Hello.
>>>
>>> I have a program that uses the webkit engine (gtk+ port) for
>>> intense-rendering. I have about 10 threads, each with it's own  
>>> webkit
>>> instance. While there's no problem when only two instances are  
>>> active.
>>> But when I increase the instances, the program segfaults.
>>
>> WebKit is not threadsafe. It is not currently possible to use it
>> safely from multiple threads. If it ever seems to work, it is only
>> through luck.
>>
>> Regards,
>> Maciej
>>