Re: "(Not Responding)" problems in Leopard
Re: "(Not Responding)" problems in Leopard
- Subject: Re: "(Not Responding)" problems in Leopard
- From: Nick Zitzmann <email@hidden>
- Date: Mon, 12 Nov 2007 20:56:24 -0700
On Nov 12, 2007, at 8:36 PM, Benjamin D. Rister wrote:
I'm not particularly trying to avoid a connection to the window
server (at least in the helper executable). I do use some API that
I noticed hooks up with the window server (NSWorkspace? Launch
Services?), so I'm mostly just trying to stay well-behaved and leave
the main run loop clear to answer the pings.
I found out the hard way a while back that, if you try using
NSWorkspace without calling NSApplicationLoad() first, then you're
playing with fire. Apple might have changed things in Leopard so that
NSWorkspace automatically sets things up, but in Tiger it didn't.
This just gets more confusing by the day, and it's shaking our
customers' confidence in the product to see the processes marked as
hung. :-/
Unfortunately I think you're going to have to avoid using any AppKit
classes in your background task.
Nick Zitzmann
<http://www.chronosnet.com/>
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden