• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: "(Not Responding)" problems in Leopard
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: "(Not Responding)" problems in Leopard


  • Subject: Re: "(Not Responding)" problems in Leopard
  • From: "Benjamin D. Rister" <email@hidden>
  • Date: Tue, 13 Nov 2007 14:59:56 -0500

Sam Stigler wrote:

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.

I reported a bug on this a while back; I haven't had a chance to try it but I think it's been fixed in Leopard.

This problem is in the opposite direction, however. Tiger is OK with these processes, it's Leopard that's complaining. Also, all actual NSWorkspace functionality is working fine and producing correct results.


Nick Zitzmann wrote:

Unfortunately I think you're going to have to avoid using any AppKit classes in your background task.

I went through the helper app and commented out everything that depended on any framework outside the explicitly-approved list of daemon-safe frameworks at <http://developer.apple.com/technotes/tn2005/tn2083.html#SECFRAMEWORKCROSSREFERENCE >, and quit linking against any of them. Activity Monitor still flagged it as not responding after running for a while.


Everything *works* from a functional standpoint. And the fact that AM is fine for a while makes me think that the fundamental structure of the loops are probably OK--a daemon instance I started yesterday is still happily hanging out without a "not responding" tag, in fact. And now it seems that it still happens even without calling anything that's not daemon-safe. Curiouser and curiouser.

Best,
br

--
Benjamin D. Rister
President
Decimus Software, Inc.

http://www.decimus.net/


_______________________________________________

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


References: 
 >"(Not Responding)" problems in Leopard (From: "Benjamin D. Rister" <email@hidden>)
 >Re: "(Not Responding)" problems in Leopard (From: Nick Zitzmann <email@hidden>)
 >Re: "(Not Responding)" problems in Leopard (From: "Benjamin D. Rister" <email@hidden>)
 >Re: "(Not Responding)" problems in Leopard (From: Nick Zitzmann <email@hidden>)
 >Re: "(Not Responding)" problems in Leopard (From: Sam Stigler <email@hidden>)

  • Prev by Date: Re: Change a NSMenu's shape?
  • Next by Date: Re: Cocoa-dev Digest, Vol 4, Issue 217
  • Previous by thread: Re: "(Not Responding)" problems in Leopard
  • Next by thread: Re: "(Not Responding)" problems in Leopard
  • Index(es):
    • Date
    • Thread