On Sat, Nov 6, 2010 at 1:47 PM, Keith Blount <keithblo...@yahoo.com> wrote: > Thanks! I just tried that but the menu item is created and destroyed by the > AppKit as far as I can see. The offending object: > > objc[88279]: FREED(id): message _bindingAdaptor sent to freed > object=0x1a4cccd0 > > Checking that object address in Instruments: > > #CategoryEvent TypeRefCtTimestampAddressSizeResponsible LibraryResponsible > Caller > 0NSMenuItemMalloc13059475443200x1a4cccd064AppKit-[NSMenu > insertItemWithTitle:action:keyEquivalent:atIndex:] > 1NSMenuItemFree03289974881280x1a4cccd0-64AppKit-[NSMenuItem dealloc]
Hmm, these are the only alloc and free events recorded in Instruments for that address? What's the backtrace on that call to -[NSMenuItem dealloc]? A bit of digging with -instancesRespondToSelector: indicates that -_bindingAdaptor is defined in a private NSObject category. So that means that the fact that it's a deallocated NSMenuItem might be a red herring. If something else was allocated at that address but prematurely freed, that could be the thing that the offending code is trying to send the -_bindingAdaptor message. Have you run the clang static analyzer (Build and Analyze) on your project? Perhaps you are overreleasing something. > (Is there a way to check the specific object that's calling it? The above is > the > only information I could find running Allocations.) Not really. All sorts of optimizations will mean that values like "self" won't remain in place for you to find them. --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
