title: iOS analysis with VM tracker. Dirty and resident memory cause memory warnings, what should I do?
body: <p><br>Hello community,
  I'm trying to debug that I didn't made. This app works online and cache all the contents on the file system saving all the paths(a lot of paths) on memory(wrong approach I see, but I must work on that). This app has an option that make download all the contents and fill the memory with the relative paths.<br> The problem is that when I check this option the app starts download and caching but before it finishes it crashes. On simulator everything works fine of course.<br>
  The crash report log talks about memory warning and app killed by jetsam.
  Tracking the app with allocation on instruments I see that the live bytes are "just" around 7Mb, this is also helped by using a flushing mechanism added during download, that releases the old paths after the download is finished.<br>
  There are no visible leaks at all.<br>
  I started to use VMTracker and I've seen that the resident and dirty memory are pretty high with peaks around 61Mb and 21Mb. There is something that I'm not getting.<br>
  I've read a lot of questions about it<br>
  <a href="https://stackoverflow.com/questions/5176074/what-do-dirty-and-resident-mean-in-relation-to-virtual-memory">What do &quot;Dirty&quot; and &quot;Resident&quot; mean in relation to Virtual Memory?</a><br>
  <a href="https://stackoverflow.com/questions/5430718/how-can-i-get-rid-of-resident-dirty-memory-in-objective-c">How can I get rid of resident dirty memory in Objective-C?</a><br>
  But since I'm releasing the most of the paths created where the other dirty memory comes from? and how can I clean it?<br>
  Thanks,<br>
  Andrea</p>