Re: Default Button heartBeat bug
Re: Default Button heartBeat bug
- Subject: Re: Default Button heartBeat bug
- From: Darkshadow <email@hidden>
- Date: Fri, 7 Jan 2005 08:08:20 -0500
Hmm, no on needing a multi-CPU machine. I've seen both the crash with
-[NSUIHeartBeat _heartBeatThread:] and the console message (not at the
same time) on my single CPU machine.
I've only seen a backtrace with NSUIHeartBeat, though; I've never seen
one with NSViewHierarchyLock.
Darkshadow (aka Michael Nickerson)
On Jan 7, 2005, at 5:38 AM, j o a r wrote:
Hej,
I have received a number of requests for the source of the sample app
that reproduces this bug. I guess the reason you might find it
interesting is if you want to verify that the bug discussed here is
the same as you might have experienced in your application?
While I don't mind sharing the code, I think that the symptoms I
posted on this list a couple of weeks ago are an equally effective way
to match a crash to this bug:
=======================================================
Symptom #1:
Backtrace contains "-[NSViewHierarchyLock lockForWriting]"
Symptom #2:
Backtrace contains "-[NSUIHeartBeat _heartBeatThread:]"
Symptom #3:
Console log "Exception *** -[NSCFArray addObject:]: attempt to insert
nil raised during heart beat. Ignoring...."
=======================================================
You might not always see all symptoms at the same time, especially not
the console log. As far as I know you also need to use a multi-CPU
machine to trigger the bug. You of course also need to have an
animation thread running in the application to trigger this bug
(that's what the heartbeat thread is used for), like for example an
animated ("pulsating") button or progress indicator.
Over and out,
j o a r
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden