Hello all, I have been chasing a memory issue that shows up when i compile with xCode5 and in the Allocations instrument. (see http://stackoverflow.com/questions/19234526/constant-app-memory-increase-ioaccelresource) . It does not register as a leak with the Leaks instrument, but i guess 1Mb per 2 minutes would qualify imnsho. The only reason i am using xThingie at the moment is that i'm prepping to submit to the AppStore, and i'm playing certificates and Archive. I completely missed that leak while running down my test suite with AppCode because it is not there !!! when i compile and run Instruments from AppCode 2.1.2, the leak is NOT there.
Also, the memory footprint is 50% higher with the xCode build vs AppCode. So my question basically, even if i use the same scheme/target, .xcodeproj file, etc etc etc .... does AppCode do anything different at compile time (switches etc ....) that may not be in my project configuration , explaining the totally different outcomes ???? if yes, please do-tell, so i can fix the ^$%()*&_ other IDE, and submit.
Another funny thing. When i build and run with AppCode, then start Instruments, and attach to the running process : voila ! the leak appears again. It could very well be an Instruments bug (given the shoddy piece of steaming sh... that xCode represent, i have even money on that).
any insights you kind peeps may give me would be appreciated. I loathe the thought of doing my final build/archive with Xcode and have my app bounce on a pseudo-leak.
Context : xCode 5 , AppCode 2.1.2, iPhone 4S test device, game uses cocos2d 2.0