[webkit-dev] WebKit bug in Dashboard widget?

[Ben Kazez]

In fact, I am calling WebKit APIs from multiple threads, which wasn't  
a good idea on my part. This is my first experience with multiple  
threads, and I'm enjoying it but am still quite a novice. My only  
WebKit call is to [WebView -stringByEvaluatingJavaScriptFromString:],  
so I've changed it to

     [_webViewLock lock];
     [_webView  
stringByEvaluatingJavaScriptFromString:endHandlerJavaScript];
     [_webViewLock unlock];

where _webViewLock is an instance variable in the Dashboard plugin  
object. However, the crash still happens -- some elements too tall,  
others too short, elements disappearing until you mouse over them,  
and then EXC_BAD_ACCESS. Should my locking code above have worked? (I  
can move this discussion to Cocoa-dev if it becomes off-topic for  
this list.)

Thank you very much for your help.

Ben

On Jul 10, 2005, at 3:18 AM, Maciej Stachowiak wrote:

>>
>> The crash is preceded by incorrect width of displayed divs,  
>> disappearing elements, or both. Does this seem to you to be a  
>> WebKit bug, or could there be a problem with my code?
>>
>
> It's hard to tell. This bug sounds likely to be some kind of memory  
> trasher, so it may be that something is corrupting memory. Is your  
> plugin calling WebKit APIs from multiple threads? WebKit is not  
> threadsafe so that is one possible cause.
>
> Can you reproduce it with just a plain web page with no plugin? If  
> so, it would definitely be a WebKit bug.
>
> Regards,
> Maciej
>