On Tue, Jul 20, 2010 at 8:41 AM, AppleLists_Jim Witte <jw.appleli...@gmail.com> wrote: > Just an idea that's probably wrong (I'm not a Cocoa programmer at all > really..). Does the user have any Unsanity APEs installed? I can't see why > an APE would be instantiating NSDocumentController (or even if it could), or > why it would occur. Would it be possible to use gdb or something else to see > whenever an NSDocumentController is instantiated, and what code is being > called around it?
You could break on +[NSDocumentController sharedDocumentController], or run in the Allocations Instrument to find the first NSDocumentController allocation event and get a backtrace from there. Any code injected into your process could ask for the NSDocumentController (haxies that deal with the menu bar seem like a prime culprit), but let's not jump straight to that conclusion. --Kyle Sluder _______________________________________________ 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
