Re: Default Button heartBeat bug
Re: Default Button heartBeat bug
- Subject: Re: Default Button heartBeat bug
- From: Shawn Erickson <email@hidden>
- Date: Thu, 6 Jan 2005 13:07:36 -0800
On Jan 6, 2005, at 12:56 PM, j o a r wrote:
On 2005-01-06, at 20.44, Dominic Feira wrote:
I have been bitten by the default button heartBeat bug. I did some
searching and it seems that this is a rather common problem, yet hard
(impossible) to fix.
Why in the world is the heartBeat running in a separate thread in the
first place? If you click on a menu or a button it stops anyway.
It'd be much safer if it were on the main thread with a timer.
I had some code that operated similary to the heartBeat and it too
crashed every once in a while, so I put it on a timer in the main
thread and it has been trouble free since. It is well known that the
AppKit is NOT thread-safe, yet apple has basic AppKit functionality
running multithreaded. Reports of this problem date back years and
yet it still isn't fixed. What gives?
I just recently managed to reproduce the problem in a sample project
that I submitted to Apple via RadarWeb. The bug is now fixed! :)
I don't know if it will be included in a patch to Panther, or if it
will be Tiger only. If you think it's an important bug to fix for
Panther (like I do), please use RadarWeb to let Apple know!
Wooohooo, thanks for taking the time to isolate the issue with a code
sample.
What is the radar number?
-Shawn
_______________________________________________
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