On Oct 3, 2011, at 8:56 PM, Quincey Morris wrote:

> On Oct 3, 2011, at 18:29 , Seth Willits wrote:
> 
>> I've been receiving reports of this rare but persistent crash over the past 
>> few years, and I've never been able to reproduce it or figure out what's 
>> causing it.
> 
> One thing you could do, if you have an actual crash dump to examine, is to 
> work out which register contains the 1st parameter to 
> [NSObject(NSKeyValueObservingPrivate) _notifyObserversForKeyPath:change:] and 
> examine the string at that location. Knowing the keypath *may* give a clue as 
> to what's going on.

All I have is the crash logs, so I can only see the register content for the 
top of the stack. I wish I could figure out how to reproduce it. In a couple 
cases they say they simply launched the app and it crashed (and that would be 
the first stack trace), but then it works fine. It's rare. I wrote a script to 
launch the thing thousands of times and I can never get it to crash. It's mega 
frustrating. 



> You could also try setting a breakpoint on setContent in one of your two 
> scenarios, and examine the object controller's observationInfo to see what 
> observers the object controller has at this point. Presumably, the (an?) 
> observer in a non-crashy situation is the object whose memory management you 
> need to suspect.

Well in the first case it's nil because there are no observers. That's why I'm 
sure it has nothing to do with the specific controller or binding. It's truly 
bizarre. 



--
Seth Willits



_______________________________________________

Cocoa-dev mailing list ([email protected])

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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to