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.
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.
The only subtle bug KVO bug that I can think of that *might* be coming into
play here is this one:
http://www.cocoabuilder.com/archive/cocoa/239182-crash-in-kvo-when-using-keypathsforvaluesaffecting-key.html
I don't know if it's ever been fixed, or whether Lion's new 'removeObserver:'
variant provides a way of avoiding that bug.
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
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 arch...@mail-archive.com
