iPhone development - memory release issue -

I'm having this issue to continue to object released from a first, but not for my life That is where the error is complete. I've added the NSZombieEnabled flag and this log I get in gdb. No one could tell me how to go about resolving this issue, or to find out that error go.

  *** - [CF string release]: message delivered allocated 0x5e4780 (GDB) # 0 0x952ff907 (in ___forwarding___ in SendEvent) # 1 (in 0x952ffa12 __forwarding_prep_0___ in NSPopAutoreleasePool) # 2 0x9260e20f () in _UIApplicationHandleEvent # 3 0x30a564b0 () # 4 0x31563dea () # 5 0x3156640c (in PurpleEventTimerCallBack) # 6 0x95280615 CFRunLoopRunSpecific in () # 7 CFRunLoopRunInMode (in 0x95280cf8) # 8 GSEventRunModal (in 0x31564600) # 9 GSEventRun (in 0x315646c5) # 10 0x30a4ec98 in - [UIApplication _run] () # 11 0x30a5a094 in UIApplicationMain () # 12 main 0x00002494 (argc = 1, argv = 0xbfffef9c) / user / Adminyuesaar / projects / Maiprosiatt / Men.amayr  

< P> thanks The.

The autoclip pool is trying to issue an object that is already released.

It may be that you can release an object registered manually Otorioj

  NSString * foo = [NSString stringWithFormat: @ "foo:% D ", 42]; [Fu release]; / * This release is bad because this object is already registered for autorelease * /  

: You can use the following method to find the point of allocation:

1. Set environment 1.
2. Run the program and once it breaks into the GDB usage from the shell to detect the stack trace of this allocation: malloc_history & lt; Pid & gt; & Lt; & Address gt; . (NSZombieEnabled will print address in GDB)

Another option (which is less likely to slow down your runtime performance) is to use the tool tool with the "zbb" template. It will track the body and will also tell you the history of the zombie without using Molok_ history command.