• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Application crash in -[NSViewHierarchyLock lockForWriting]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Application crash in -[NSViewHierarchyLock lockForWriting]


  • Subject: Re: Application crash in -[NSViewHierarchyLock lockForWriting]
  • From: j o a r <email@hidden>
  • Date: Sun, 5 Dec 2004 16:56:28 +0100


On 2004-12-05, at 13.32, John C. Randolph wrote:

The problem is, neither has anyone else.

I never said it was going to be easy... ;)

I'm sure it's a timing / race condition. I think it's a really bad bug, as it's a crasher, it's in core functionality (buttons), and since it's practically no way for a third party developer to work around it - at least not without really nasty hacks...
I understand just how boring it must be for the responsible developer(s) to try to track it down without a reproducible case, but for really nasty bugs you still have to try. Granted, for all I know you might have tried already, but I have my doubts, as it's still with us after more than two years.


The way I see it, if you can't make the threaded animations work reliably, there need to be a way for us to disable them. We deploy our applications in an environment where random crashes, like the ones triggered by this bug, is not acceptable. It makes us look very bad to our customers.

I've seen this symptom a few times myself, and a few developers have reported it to me personally, but when they see it, it's typically showing up for about one out of a hundred of their users once every couple of weeks. My guess is that it's timing-dependant, which is why it shows up so rarely. (The heartbeat thread finishes its drawing very quickly.)

It happens in Xcode at least once per day on my machine. I'm sure I could provoke it to happen more often if I tried. I'm thinking about creating some sort of stress-test-application that might be able to trigger it reliably. I'll see if I can find some time to do that this week.


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

References: 
 >Application crash in -[NSViewHierarchyLock lockForWriting] (From: j o a r <email@hidden>)
 >Re: Application crash in -[NSViewHierarchyLock lockForWriting] (From: "John C. Randolph" <email@hidden>)

  • Prev by Date: Re: Best way to debug (was retain/release/pointers question)
  • Next by Date: Getting file icon in authorised executable
  • Previous by thread: Re: Application crash in -[NSViewHierarchyLock lockForWriting]
  • Next by thread: Problems with NSApplication Delegates
  • Index(es):
    • Date
    • Thread