Re: CFMessagePort problems
Re: CFMessagePort problems
- Subject: Re: CFMessagePort problems
- From: Paul Kim <email@hidden>
- Date: Mon, 4 Dec 2006 14:04:05 -0500
Thanks for the response.
I suspect that some APE/InputManager was creating an NSApplication
but I'm not sure if I'm ready to write them all off as that.
I'm curious as to the error code. In your TextEdit example, you got a
1103 (BOOTSTRAP_SERVICE_ACTIVE) which makes sense whereas in the
cases I'm seeing, it's a 1100 (BOOTSTRAP_NOT_PRIVILEGED). Not sure
how much of a difference that makes nor do I know how to interpret
that error.
Paul Kim
------------------------------------
Chief Noodler - Noodlesoft
email@hidden
http://www.noodlesoft.com
On Dec 4, 2006, at 1:09 PM, John Stiles wrote:
I don't think AppKit is designed to run multiple copies of an app
at once. If you try the same thing with TextEdit, you get similar
looking messages:
~ jstiles$ cd /Applications/
/Applications jstiles$ ./TextEdit.app/Contents/MacOS/TextEdit &
[1] 343
/Applications jstiles$ ./TextEdit.app/Contents/MacOS/TextEdit &
[2] 344
2006-12-04 10:07:13.046 TextEdit[344] CFLog (0): CFMessagePort:
bootstrap_register(): failed 1103 (0x44f), port = 0x3103, name =
'com.apple.TextEdit.ServiceProvider'
See /usr/include/servers/bootstrap_defs.h for the error codes.
2006-12-04 10:07:13.046 TextEdit[344] CFLog (99):
CFMessagePortCreateLocal(): failed to name Mach port
(com.apple.TextEdit.ServiceProvider)
It's entirely possible that, while your app doesn't create a run-
loop or NSApplication object, some APEs/Input Managers are doing
this on your behalf. This could be something to investigate.
On Dec 3, 2006, at 1:39 PM, Paul Kim wrote:
Hi,
I have a commandline/background program. It's written in Objective-
C and uses Foundation. It is started by launchd and when it runs,
it does it thing and then exits. It does not explicitly create an
NSApplication or run loop.
In the past week or so, I've suddenly received bug reports from
users of the following form:
2006-12-03 19:53:03.552 hazelfolderwatch[566] CFLog (0):
CFMessagePort: bootstrap_register(): failed 1100 (0x44c), port =
0x2103, name = 'NSApplication-MainThread-236-8471333827395#'
2006-12-03 19:53:03.553 hazelfolderwatch[566] CFLog (99):
CFMessagePortCreateLocal(): failed to name Mach port
(NSApplication-MainThread-236-8471333827395#)
2006-12-03 19:53:03.553 hazelfolderwatch[566] *** Assertion
failure in -[NSApplication _createWakeupPort], AppKit.subproj/
NSApplication.m:3578
2006-12-03 19:53:03.554 hazelfolderwatch[566]
CFMessagePortCreateLocal returned NULL port
The way it's described by users, it starts happening all of a
sudden. It is common to have multiple copies of this process
running and I have not had issues with running multiple copies of
the program for the 2+ months the product has been out (plus the
months of alpha/beta). It's not an application per se and does not
use mach ports directly.
At least in one case, uninstalling some Application Enhancers did
remedy the problem but I don't feel confident that APE's or Input
Managers are responsible for all the cases I am seeing.
If anyone has any insight into what is going on here and why I'm
getting multiple reports coming in out of nowhere. Also, any tips
on how to diagnose, fix and/or work around this would be greatly
appreciated.
Thanks,
Paul Kim
------------------------------------
Chief Noodler - Noodlesoft
email@hidden
http://www.noodlesoft.com
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
40blizzard.com
This email sent to email@hidden
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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