Re: Should I care about this error message?
Re: Should I care about this error message?
- Subject: Re: Should I care about this error message?
- From: Doug Wyatt <email@hidden>
- Date: Wed, 27 Jul 2005 12:03:03 -0700
The message suggests that the client-side code of CoreMIDI is trying
to register a mach port for communication with the server, but such a
port already exists. That could happen if the server crashed and the
client-side code attempts to recover, unsuccessfully.
I suspect ~/Library/Logs/CrashReporter/MIDIServer.crash.log will
contain crash reports around the same time as the console log messages.
I've seen a number of MIDIServer crash reports from the wild, and
well over 90% of them are in the code of a few misbehaving drivers.
Doug
--
Doug Wyatt
Core Audio, Apple
On Jul 27, 2005, at 3:13, Marco Hinic wrote:
In the console I see this occasionally.
No error message is being propagated in my code, so I suppose it's
being
handled internally in Core Audio.
However some customers are complaining about loosing MIDI in my
application.
Here is the message:
2005-07-27 12:08:31.052 ArKaos[258] CFLog (0): CFMessagePort:
bootstrap_register(): failed 1103 (0x44f), port = 0x62db, name =
'Apple
MIDI Client 258'
See /usr/include/servers/bootstrap_defs.h for the error codes.
2005-07-27 12:08:31.053 ArKaos[258] CFLog (99):
CFMessagePortCreateLocal
(): failed to name Mach port (Apple MIDI Client 258)
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden