Re: Crash in CFRunLoopWakeUp
Re: Crash in CFRunLoopWakeUp
- Subject: Re: Crash in CFRunLoopWakeUp
- From: Greg Parker <email@hidden>
- Date: Thu, 3 Sep 2009 16:04:55 -0700
On Sep 3, 2009, at 3:41 PM, Mark Allan wrote:
I've been battling with this intermittent crash for about two weeks
now and can't figure it out for the life of me. I've got try/catch
blocks around nearly all my code, and definitely around any code
which runs in a separate thread, but it's not catching whatever
causes this crash. Also, I'm not even convinced it's my threads
causing the crash as this one happened while a modal sheet was being
displayed, before any of my external threads got started.
Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000001, 0x0000000090d5c02c
Crashed Thread: 6
Thread 6 Crashed:
0 com.apple.CoreFoundation 0x90d5c02c CFRunLoopWakeUp + 156
1 com.apple.Foundation 0x903ad0e4 _backgroundActivity +
440
EXC_BREAKPOINT means the process deliberately killed itself (including
`int3` on i386, `trap` on ppc, `__builtin_trap()` in gcc). In the case
of CFRunLoopWakeUp(), it's halting because it tried and failed to send
a Mach message to that run loop. Most likely this means the target run
loop has already been deleted, but other Mach messaging problems are
possible.
_backgroundActivity is part of NSFileHandle, to perform things like -
readInBackgroundAndNotify. Perhaps there's bad memory management of an
NSFileHandle somewhere.
--
Greg Parker email@hidden Runtime Wrangler
_______________________________________________
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