title: Strategies for "realistically" testing low memory conditions in iOS Simulator
body: <p>I'm at a point in the development of <a href="http://github.com/GarrettAlbright/wptrans" rel="nofollow noreferrer">my little app</a> where I'm implementing didReceiveMemoryWarning and such, but I feel like I don't have a good grasp on the best way to test what I'm implementing.</p>
  
  <p>First off, apparently in the simulator, didReceiveMemoryWarning isn't triggered for apps that aren't in the foreground <em>until</em> that app is brought back into the foreground, according to <a href="https://stackoverflow.com/questions/6078090/not-getting-didreceivememorywarning-when-app-is-in-the-background">this question</a> - actually, that matches my own experience, but I was prone to ignore it because it doesn't really make sense. (Why would I want to delay clearing up my memory until I'm coming back into the foreground and probably about to need that data again?) Does this match the behavior of actual hardware? If so, does it make sense to cleanup tasks in applicationWillEnterBackground in addition to didReceiveMemoryWarning?</p>
  
  <p>Second, generally, what is a good strategy for triggering the "Simulate Memory Warning" menu item in the simulator in such a way as to trigger memory warnings in a manner that they're likely to happen on the actual hardware?</p>