> On 5 Jul 2016, at 02:35, Jens Alfke <j...@mooseyard.com> wrote: > > Operating systems behave differently with regard to overcommitting. I’m not > very familiar with Linux and almost totally unfamiliar with Windows. My > understanding is that Linux has some kind of “OOM Killer” process that will > kill any process that’s using too much memory; presumably this happens before > that process would run out of allocatable space. At the other extreme, iOS > doesn’t use swap space at all and will kill a process that tries to use too > much of physical RAM.
I know that Solaris (and derivative) systems explicitly don’t overcommit - if malloc returns a pointer it means that memory is all available, and there are no surprise aborts when you happen to touch a new page. Overcommitting is popular though, and Linux’s malloc is - like OS X’s - also able to return a pointer and kill your program when you try to use it. Chris _______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list (Xcode-users@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/xcode-users/archive%40mail-archive.com This email sent to arch...@mail-archive.com
