• 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
Application crash in -[NSViewHierarchyLock lockForWriting]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Application crash in -[NSViewHierarchyLock lockForWriting]


  • Subject: Application crash in -[NSViewHierarchyLock lockForWriting]
  • From: j o a r <email@hidden>
  • Date: Sat, 4 Dec 2004 11:38:40 +0100

Hej,

There is a serious bug in Mac OS X / AppKit that can cause crashes in any application that uses animations in background threads, as provided by default by for example NSProgressIndicator, the default button cell in a window, et.c.

The purpose of this message is to encourage all of you to file bug reports on this problem if you ever see it.

My bug reports on this problem has been marked as "duplicates" (the one I'm tracking now is case 3858351), but as bug reports works as "votes" when it comes to setting the priorities for Apples engineering efforts, I firmly believe that it it would make a lot of sense for you to file new bug reports for this crash.
What I think Apple would need the most is a reproducible case. I have unfortunately not been able to provide one.


I see this crash bug a lot in Xcode, but I have also seen it in ProjecBuilder, Mail, and our customers are reporting that it happens in the application that our company is developing.

=======================================================

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.
I think that you need a multi-CPU machine to reproduce this problem, but I'm not quite sure.
Our application, PB, Xcode and Mail all share the characteristics of having a lot of background threads that funnel data into the main thread. That's probably also related to this problem.


The first time I reported this crash to Apple was in October 2002 so I would really like to see it fixed soon. I hope it's not too late to hope for a fix in Tiger!

Thank you!

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

  • Follow-Ups:
    • Re: Application crash in -[NSViewHierarchyLock lockForWriting]
      • From: "John C. Randolph" <email@hidden>
  • Prev by Date: Re: Starting as Startup Item?
  • Next by Date: Re: Inserting a custom class into class hierarchy?
  • Previous by thread: Re: Starting as Startup Item?
  • Next by thread: Re: Application crash in -[NSViewHierarchyLock lockForWriting]
  • Index(es):
    • Date
    • Thread