Re: Beach balling on mach_msg_trap
Re: Beach balling on mach_msg_trap
- Subject: Re: Beach balling on mach_msg_trap
- From: Ken Thomases <email@hidden>
- Date: Wed, 21 Oct 2009 17:18:47 -0500
On Oct 21, 2009, at 2:17 AM, Nathan Day wrote:
I am getting a beach balling in an application I am working on, I
would of investigated more but I have noticed that some other apps
on my computer seem to be doing the same thing.
If I move my applications window it free up the block allowing an
event to be processed), but the instantly freezes on the next event,
this is why I think other applications have the same problem because
they exhibit the same behaviour, this includes the Applications
Safari when playing a movie, Quick Time Player but the sound keeps
playing and a Third party app called Opacity. s this a known issues.
It doesn't affect my MacBook Pro only my iMac and the issue occurred
in 10.5 and 10.6, I am using an NSOperationQue which may have
something to do with it.
One thing that is different between my MacBook Pro and iMac is that
my iMac is nearly always doing something in the background, without
may app running there is about 15% to 20% cpu usage and about 500
thread, another difference between my iMac and my MacBook Pro is
that my iMac has only 37% of 1TB hard disk space, I have heard there
can be some issues with disk fragmentation at 30% or less hard disk
space.
(gdb) where
#0 0x000000010011ad7a in mach_msg_trap ()
#1 0x000000010011b3ed in mach_msg ()
#2 0x000000010047fce2 in __CFRunLoopRun ()
#3 0x000000010047f03f in CFRunLoopRunSpecific ()
#4 0x000000010242ac4e in RunCurrentEventLoopInMode ()
#5 0x000000010242aa53 in ReceiveNextEventCommon ()
#6 0x000000010242a90c in BlockUntilNextEventMatchingListInMode ()
#7 0x0000000100fc1520 in _DPSNextEvent ()
#8 0x0000000100fc0e89 in -[NSApplication
nextEventMatchingMask:untilDate:inMode:dequeue:] ()
#9 0x0000000100f86a7d in -[NSApplication run] ()
#10 0x0000000100f7f798 in NSApplicationMain ()
#11 0x00000001000034ba in main (argc=1, argv=0x7fff5fbff3c8) at
XXXXXXXXXX
This stack trace does not indicate an app that is stuck. It indicates
the normal state of an app which is waiting for (and should be
responsive to) events.
I doubt NSOperationQueue has anything to do with the symptoms you're
seeing.
The fact that several applications are showing similar symptoms
suggests there's something wrong with your Mac or your user account.
I would try creating a new user account and seeing if the problem
persists there. Remove or disable any third-party kernel extensions,
input managers, contextual menu plug-ins, haxies, etc. Repair and
Repair Permissions on your boot volume. If necessary, reapply the
most recent Combo update to the OS, or even do an Archive and Install
(although 10.6 eliminated this option).
Unfortunately, if none of this helps, you should take this to a
general diagnostics discussion forum. I don't think it has anything
to do with Cocoa development.
Good luck,
Ken
_______________________________________________
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