CODEWITHSUNDEEP
iphoneobjective-cioscocoa-touch
Jules
Jules

Reputation: 7774

How do I fix the error 'No memory available to program now: unsafe to call malloc'?

How do I debug and fix this error

No memory available to program now: unsafe to call malloc

Analyser doesn't show any cause.

Upvotes: 3

Views: 743

Answers (1)

zaph
zaph

Reputation: 112865

Use instruments to check for leaks and memory loss due to retained but not leaked memory. The latter is unused memory that is still pointed to. Use Heapshot in the Allocations instrument on Instruments.

For HowTo use Heapshot to find memory creap, see: bbum blog

Basically there method is to run Instruments allocate tool, take a heapshot, run an intuition of your code and another heapshot repeating 3 or 4 times. This will indicate memory that is allocated and not released during the iterations.

To figure out the results disclose to see the individual allocations.

If you need to see where retains, releases and autoreleases occur for an object use instruments:

Run in instruments, in Allocations set "Record reference counts" on on (you have to stop recording to set the option). Cause the picker to run, stop recording, search for there ivar (datePickerView), drill down and you will be able to see where all retains, releases and autoreleases occurred.

Upvotes: 4

Related Questions