CODEWITHSUNDEEP
iphoneobjective-cxcodememory-management
Srinivas
Srinivas

Reputation: 1059

memory leakage in system libraries

below is my memory leakeage . i cant identify were its leaking but 6 leakage is there. in grouping column when hide my system libraries i checked means below leakeage is not showing.( in image lefthand side bottom u een this grouping column). problem is my sytem libraries or something else.

enter image description here

i already wasted 2 days so only am asking here. help in this.

Were is leakege?

Upvotes: 3

Views: 633

Answers (5)

TabishFarooqui
TabishFarooqui

Reputation: 156

As far as I can gather from the image, there seems to be some kind of background thread running constantly...be it a system library or some object which is not properly released. Such issues really are a bottleneck in development. It becomes really complex to find out the exact point where the leak is occurring.

Build and Analise is a good option, since it will give you a proper path as to where and why the leak is occurring!!

Best of luck!!

Upvotes: 2

Kendall Helmstetter Gelner
Kendall Helmstetter Gelner

Reputation: 75058

Did you try this on the device? Sometimes you can see leaks in the simulator that do not show up on the device.

Upvotes: 0

bbum
bbum

Reputation: 162712

Is the problem in my system libraries, or something else?

(Highlighting OP's question, since whoever thinks this needs to be closed didn't see it. Perfectly valid question.)

The leaks appear to be entirely in the system; it is possible for such a leak to be caused by your code indirectly, but it is extremely unlikely.

It could also be a false positive; the system is playing games with a pointer such that a reference does still exist.

In any case, file a bug via http://bugreport.apple.com/.

If you don't see growth over time -- if the leak is limited to 6 ~32 byte allocations for the runtime of your app -- then it isn't something to worry about beyond the annoyance of being there.

Upvotes: 4

elp
elp

Reputation: 8131

You need to alloc and release all object correctly, that is not easy, but necessary.

You can enable another control from build options: RUN_CLANG_STATIC_ANALYZER to show all wrong release at compile time

See this answer: iPad View Controller Memory Management

hope this helps.
A

Upvotes: 0

David Gelhar
David Gelhar

Reputation: 27900

Based on the call stack in the screenshot, it looks like all the calls are inside system libraries, running on a background thread. libGLProgrammability.dylib is probably OpenGL, which appears to be running LLVM internally.

Does the leak grow over time? If not, since there are only 6 objects (total 192 bytes) showing as leaked you probably don't want to make yourself too crazy about this...

Upvotes: 1

Related Questions