0

I am implementing an iPhone application and when I ran this app initially it was showing memory size was 5.3MB

enter image description here

and after 10 min it was showing memory size was 185.3 MB.

enter image description here

I'm releasing objects manually and also analyzed my app, I have only one memory leak(that to return object in class method). What was the problem? is it harm to app while apple approve it?. Please help me. Thanks in advance.

Ganesh G
  • 1,991
  • 1
  • 24
  • 37
  • If it is constantly growing it is something that would be addressed.. What is your app doing when its growing? Is it when you are creating these objects you say are leaking? – RyanG Dec 09 '13 at 14:07
  • My app is running smoothly and we are not getting any crash issues. – Ganesh G Dec 09 '13 at 14:12

3 Answers3

2

No, you really shouldn't release it with this kind of a leak (or memory accretion). It will lead to crashes and that will cause data loss and upset users.

Heapshot analysis is designed to track down these kinds of problems. That is, use the Allocations Instrument to track memory growth over time iteratively and then eliminate the large memory consumers.

bbum
  • 162,346
  • 23
  • 271
  • 359
0

Apple will probably approve it as long as it is not crashing within the review time.

But no you should not release the app if you have a memory leak like this. Your app will have poor user experience and might crash if the users device memory runs full. You will get a low app store rating.

I would suggest you find out which object is taking up so much memory and fix it. If at all possible switch to ARC, this will take away some leaks.

Joshua
  • 15,200
  • 21
  • 100
  • 172
rckoenes
  • 69,092
  • 8
  • 134
  • 166
  • Now I can't move to ARC as we have a less time to complete it. – Ganesh G Dec 09 '13 at 14:14
  • I have pushed app which was having more then 10 leaks and the app got approve from apple long back. – Ganesh G Dec 09 '13 at 14:15
  • 1
    I'm not saying that Apple wil not approve your app, but having memory leaks in you app is just not acceptable. If the memory leaks make you app crash expect many negative reactions in the app store. – rckoenes Dec 09 '13 at 14:17
0

I have same problem too. NSZombieEnabled flag work for me. I think this might be helpful to cope up with ARC. I have followed this link: How do I set up NSZombieEnabled in Xcode 4?

Community
  • 1
  • 1
RamGrg
  • 296
  • 1
  • 4
  • 20