Agent process shown as "non responding" in Activity Monitor

[Eric Peyton]

An app listed as "non responding" in Activity Monitor is listed that  
way because it registers with the window server but at a certain point  
stops servicing window server calls and callbacks.  This can happen in  
daemons/agents if you check in and then run your own internal run loop  
for example instead of the NSApp/Carbon run loops.

You can avoid this in a few different ways.

a)  Don't register with the window server.  Do your agents really need  
UI?
b)  Service the app run loop

Eric

On Jul 18, 2008, at 3:36 AM, Jérôme Seydoux wrote:

> Hi,
>
> My app has a few agent processes (with no carbon event loop nor cocoa
> NSApp, but that can use some other carbon or cocoa APIs). They are
> sometimes shown as "non responding" in Activity Monitor on 10.5. They
> are bundled executables, with a basic Info.plist file:
> 	<key>CFBundleDevelopmentRegion</key>
> 	<string>English</string>
> 	<key>CFBundleExecutable</key>
> 	<string>FTFileCrawler</string>
> 	<key>CFBundleInfoDictionaryVersion</key>
> 	<string>6.0</string>
> 	<key>CFBundleName</key>
> 	<string>FTFileCrawler</string>
> 	<key>CFBundlePackageType</key>
> 	<string>APPL</string>
> 	<key>LSBackgroundOnly</key>
> 	<true/>
> 	<key>CFBundleIdentifier</key>
> 	<string>com.ctmdev.FoxTrotFileCrawler</string>
> 	<key>CFBundleSignature</key>
> 	<string>FTb3</string>
>
> Is there something I can do to avoid that?
>
> Thanks
>
> _______________________________________________
> MacOSX-dev mailing list
> MacOSX-dev at omnigroup.com
> http://www.omnigroup.com/mailman/listinfo/macosx-dev
>