iPhone Memory Debug with NSZombie and Instruments
Why Stack Overflow recommends it
Stack Overflow users link it when answering EXC_BAD_ACCESS and over-release questions in iOS apps, because it shows how to find the offending object with NSZombie and Instruments.
Recommended by 5 people across 4 different months, 2010 to 2014.
What it is
A six-minute screencast showing how to enable NSZombie in Xcode's Instruments to track down an EXC_BAD_ACCESS memory crash in an iPhone app. It walks through the Zombies instrument and reading its output. Presented by Mark J of smartpumadotcom.
What people said
Recommends Cezar Alexandru Vancea · 2010-09 · Stack Overflow · on “Strange Exc Bad Access when using Init, PushViewController, Release. Anything wrong with this code?”
Haven't even read your post. If it's Exec-Bad-Access, I have 2 words for you: Enable NSZombies. Follow this link: (it explains everything you need to know to fix any bad access issue) Phone Memory Debug with NSZombie and Instruments [this video] Cheers!
Recommends Josh Sherick · 2011-06 · Stack Overflow · on “EXC_BAD_ACCESS error help”
Memory Management can be confusing at first. Only release objects that you have created. This is almost only if you use the words alloc, init, retain. The problem in your case is that you do not actually own the object, it is autoreleased, because you did not alloc, init or retain it. This is fine, but it is not your job to release it, so don't worry about it. If you get "EXC_BAD_ACCESS" errors later, it might be helpful to use NSZombies [this video] to help find where you are releasing incorrectly. They work by placing a "zombie" in memory wherever you release an object so it is easier to tell what the problem is. EDIT: For example, say you have: NSString *foo = [[NSString alloc] initWithString:
Recommends Midhun MP · 2012-08 · Stack Overflow · on “Xcode Instruments - Zombies - what am I looking for?”
You will get the leak above the object allocation bar. Check this image; For a reference, check this video [this video]
Recommends Pfitz · 2012-08 · Stack Overflow · on “How to read this iphone app crash log”
This is a stacktrace you see the stack of methods called when the crash happened. You start at the bottom and work yourself up to the top and search for a method call from your app (the stacktrace includes calls from the frameworks too (e.g. -[UIScrollView(Static) _adjustContentOffsetIfNecessary] )). The topmost method call from your app is likely the cause of your error and you can see what the system tried afterwards. In your case it seems that you call popToViewController and the iOS frameworks try to animate the transition from one UIViewController to the next. There seems to be a problem for the table view to set its frame and scroll to the contentOffset. This is likely to be caused by
Recommends Tibor Udvari · 2014-01 · Stack Overflow · on “EXC_BAD_ACCESS (code=1, address=0x0) when runModalForWindow”
the best way to debug EXC_BAD_ACCESS errors is to use NSZombies . Check out this video for an explanation : [this video] NSZombie keeps all your objects in memory when you are trying to release an object that has already been released, so you get closer to finding your bug. As @Mark H said, it is a memory management issue. Also you could put an NSLog in your dealloc method to have a better idea of what is getting deallocated when at runtime.
Cites R. Dewi · 2011-04 · Stack Overflow · on “how to using NSZombieEnabled on intrument Xcode 3.2.5”
i have some problem in memory management, and then i try to fix it using intrument tool. Base on mark j video on you tube [this video] about using NSZombieEnabled in intrument, i try to do like that. The problem is i never find a checkbox to set NSZombieEnabled active in my instrument. In this case i use xcode 3.2.5 and still on IOS 4.2. This is the screenshot from the instrument that show no one check box for NSZombieEnabled activated : am i doing something wrong?? help me please thank you