That trace is rather meaningless without access to the code. My suggestion would be to download and install the Clang Static Analyzer and run your code against it to determine where the leak exists. It can be found at http://clang.llvm.org/StaticAnalysis.html - to use it, copy the contents of the .tar.gz file to /usr/bin then cd to your Xcode project and run scan-build xcodebuild
. At which point you'll be given output that directs you to copy and pate a line that resembles scan-view /tmp/logs/...
That should give you some indication.
+1
A:
wisequark
2008-12-06 07:06:32
A:
You need to click the "View" button in the upper right of Instruments and choose "Extended Detail" then click the line item as you have selected above then click the details in the Extended Details right hand side column and it will open up to the line of code at fault in XCode
Brent Ramsey
2010-01-29 20:55:21