_dyld_start causes leaks in iphone applications

Using the "Selection" tool on my Iphone, I notice in my snapshots that all heap growth is caused by the calling _dyld_start (dyld libraries).

Here is an example:

Snapshot: UIImageView
Heap Growth: 4.83 Kb
Still Alive: 103

When I look through the details, all I see are a few examples of the following:

Object Add: xxxx
Creation Time: ....
Live: check
Responsible Library: dyld
Responsible Caller: _dyld_start
  • What does it mean?
  • How can I change my code to free this memory?
+3
source share
1 answer

if you load your UIImage using imageNamed: then you cannot release it.

call imageNamed: caches the image until the application closes.

you can try loading ur Image using imageWithContentsOfFile: or imageWithData:

,

0

Source: https://habr.com/ru/post/1770008/


All Articles