• 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: Mon, 12 Nov 2007 22:36:53 -0500

No Carbon UI functions, though plenty of Carbon FS functions. No call to NSApplicationLoad(), either--my understanding is that that's only needed if you're trying to run a Carbon event loop and use Cocoa.

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.

As a further bit of weirdness, I just noticed that it takes a while for Activity Monitor to get upset with the processes, and sometimes won't even ever flag them. The daemon, for instance, will be just fine when launched and interacted with, and I'll just find it marked as not responding some time later when I happen to look (but still producing samples like the ones I already posted).

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. :-/

Best,
br

On Nov 12, 2007, at 3:58 PM, Nick Zitzmann wrote:


On Nov 11, 2007, at 8:17 PM, Benjamin D. Rister wrote:

Can anybody shed some insight on what the problem is? As far as I can tell, the processes are being well-behaved, so I'm rather at a loss as to why this is happening...


Only the Activity Monitor people would know for sure, but in my experience, the "not responding" appears if a task opened a connection to the window server, and then did not respond to "ping" Apple events. Does your task call NSApplicationLoad() or use any Carbon UI-related functions?

Nick Zitzmann
<http://www.chronosnet.com/>





-- 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


  • Follow-Ups:
    • Re: "(Not Responding)" problems in Leopard
      • From: Uli Kusterer <email@hidden>
    • Re: "(Not Responding)" problems in Leopard
      • From: Nick Zitzmann <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>)

  • Prev by Date: Re: Notification when switching Spaces?
  • Next by Date: Re: A window that moves on the active space
  • Previous by thread: Re: "(Not Responding)" problems in Leopard
  • Next by thread: Re: "(Not Responding)" problems in Leopard
  • Index(es):
    • Date
    • Thread