On Jul 29, 2012, at 3:28 AM, Martin Hewitson <martin.hewit...@aei.mpg.de> wrote:
> I have a document based app which uses ARC. I have occasional crashes when > closing a document. I'm guessing it's a memory issue somewhere, but I'm > looking for clues as to where to start looking, or how to sensibly debug > this. The backtrace looks like this: > > * thread #1: tid = 0x2503, 0x00007fff8c7682d0 libobjc.A.dylib`objc_msgSend + > 16, stop reason = EXC_BAD_ACCESS (code=13, address=0x0) > frame #0: 0x00007fff8c7682d0 libobjc.A.dylib`objc_msgSend + 16 Any time you crash in objc_msgSend, the issue is probably a prematurely-deallocated object (or another way of putting it, a dangling reference), and you should turn on Zombies in the Diagnostics tab of the Run view of the scheme editor. That way, next time it crashes, it will probably tell you the class of the deallocated object it was trying to message. —Jens _______________________________________________ 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
