On Thu, Apr 22, 2010 at 11:09 AM, Hao Lü <ryan....@gmail.com> wrote: > I did not see such exceptions been thrown, nor any crash....
Those are two possible responses the code could have. It could also just abort the thread, or perhaps act errantly because data it expects is not the data it has, by virtue of being on a separate thread (accessing thread-local storage assuming you're always on the main thread would be a good example). > Doubt it. I am using a secondary hidden webView dedicated to the background > thread. I was not sure if "@synchronized" would help, so I added anyway upon > each access. But it did not make a difference. I feel that if it was caused > by things related to "thread-safe", linking a seperate WebKit might not > help. The suggestion was to download the WebKit source and build it so you could trace through it with the debugger to see what actually happened inside WebKit. If your idea of fixing thread safety is to throw in @synchronized because you're unsure if it could help, you will not be able to fix your threading problems. To start, @synchronized doesn't change the current thread of execution. --Kyle Sluder _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
