iOS Can An App Be Rejected For Any Leakage?

[kalimba]

I'm just getting started on my next application, and I'm already seeing a minor (possibly unfixable) leak supposedly coming from the OpenGL library. My questions are:

(1) Would Apple normally reject an application for a very minor leak? The leaks I'm seeing total something on the order of ~500 bytes.

(2) If Apple does reject for such minor leakage, what if the leaks are from Apple library code?

(3) Is anyone else seeing leakage in their OpenGL application that is attributed to 'glvmgenerateModularFunctionPointer'?

 

[wakka092]

500 bytes? I would be very surprised if they rejected your app for a leak that small.

 

[chbeer]

I use the XMLParser for my application and there seems to be a leak, too. But Apple never rejected my app because of that.

 

[biosopher]

I'm seeing 'General Block' leaks in libGLProgrammability.dylib's glvmGenerateModularFunctionPointer.

It's rather annoying because I prefer to have a clean memory test. So far, there seems to be nothing that I can do.

There is more info here if you have access to Apple's beta iPhone Forum:
https://devforums.apple.com/message/37364#37364

BTW, did your app have problems getting accepted due to the leak?

Anthony

 

[nottooshabby]

I'm seeing 'General Block' leaks in libGLProgrammability.dylib's glvmGenerateModularFunctionPointer.

It's rather annoying because I prefer to have a clean memory test. So far, there seems to be nothing that I can do.

There is more info here if you have access to Apple's beta iPhone Forum:
https://devforums.apple.com/message/37364#37364

BTW, did your app have problems getting accepted due to the leak?

Anthony

I'm fairly certain they don't reject apps for leakage, unless it's so bad that your app crashes while they are reviewing it.