From: kimura w. <ki...@us...> - 2005-04-17 13:50:30
|
Hi, I added this problem to the tracker on sf.net. Fri, 15 Apr 2005 13:40:33 +0100, Jonathan Paisley wrote: >Hi all, > >Following up from my earlier thread "Thread scheduling", I've >identified the precise cause of the problems I've been seeing. > >As I see it, this means it is never safe to use any objective c calls >from the non-main Ruby thread. > I get it. >Setting rb_thread_critical for the lifetime of each NSAutoreleasePool >or exception context should resolve the issue, but means that >concurrency is prevented during all Cocoa calls. I shall investigate >how this affects the application I'm working on. > I'm looking for reading your next report. Thanks a lot! |