CODEWITHSUNDEEP
iphonememory-managementapp-storesubmitinstruments
Nitin
Nitin

Reputation: 7471

Is it ok to submit application with following issue?

I have developed application and all is well. As well, I also keep memory foot print very low.No leaks show during application run. I tested application more than two hour and there is no crashing report. But when i checked application on instruments at that time it's show me following leaks.I have checked my app but there is no such leaking object. "Even I used app continue 12 hour and it didn't crash or stop".

//Here the screen shot of instruments.

enter image description here

///>>>>>>Here, I uploaded latest screenshot of leaks.It may help somebody to understand where the leak is. // I think it's library file leaks(CoreFoundation)...Please Suggest What to do..

enter image description here

Please help me, This is really screw me up.

Thanks.

Upvotes: 0

Views: 143

Answers (2)

user1079903
user1079903

Reputation:

Hey analyze you code using "command+shift+b" and fix all leaks whatever coming after analyzing, submit it to app store. I don't think we can fix all leaks shown by instrument, so better to go with command+shift+b. I think we should use instrument only when getting memory warning and crashes due to insufficient memory.

Upvotes: 2

lukasz
lukasz

Reputation: 771

Not all of the 'memory leaks', are actual leaks. And some of the reported issues may be caused by Apple libraries themselves. Typically all the singletons, static variables, and some c level variables are 'leaked', but only once and are not considered a threat to memory.

Foundation classes such as NSString, NSArray, etc. are optimized to handle heavy workload. And some objects may be kept in the memory to be reused later. Such as @"".

So unless the issue is accumulating over time, just go for it, submit your app as it is. You still can fix it later, if necessary.

Upvotes: 2

Related Questions