[webkit-dev] segfault when having multiple webkit instances (got backtrace)
oliver at apple.com
Mon Oct 6 02:18:11 PDT 2008
No amount of locking will save you -- webkit uses many threads itself
-- many (if not most) of which then post messages directly to the main
application thread, on the assumption that all webviews are being
controlled by that one thread.
On Oct 6, 2008, at 1:24 AM, Luka Napotnik wrote:
> 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
> 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:
>>> I have a program that uses the webkit engine (gtk+ port) for
>>> intense-rendering. I have about 10 threads, each with it's own
>>> instance. While there's no problem when only two instances are
>>> 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.
> webkit-dev mailing list
> webkit-dev at lists.webkit.org
More information about the webkit-dev