![Uninstaller Uninstaller](http://i.imgur.com/TyXKz.jpg)
I am a university student who has been trying to write a compare and contrast paper between how Windows, Linux, and Mac OS X manage memory. For instance, with Windows, it's physical memory (RAM) and virtual memory (paging file). How does a Mac do this? So far, the only information I've found on the topic has been people screaming about one of the releases for Mac OS X and how it had memory leaks. Please keep in mind, I am not a Mac user, so I'm not looking for instructions on how to check memory being used, etc. A link to an article or document that explains how it works would be most appreciated.
I found this:, but it deals more with garbage collection in Objective-C than the OS's internal memory management. Apple documents the lowest levels of the and the virtual memory subsystem fairly well on the web as part of it's developer documentation. • Since that kernel was, you can find dozens of describing it quite easily. If that is too low level for your paper, we have easily 10 or more good questions covering more of a non-programmer's view of OS X memory management. You'll probably have to do the synthesis of how OS X compares to the other two OS as I haven't seen that answered here to date. Focus on the and tags for the best results in your searching: • • • • • By the sheer number of 'inactive memory' questions, you can focus on the part of OS X's memory management that is most puzzling to people and hence gathers the most questions here looking for explanations.
So maybe you have a lot of mods and your minecraft keeps crashing because you don't have enough memory to run minecraft so it keeps crashing. This is a tutorial for how to do this on a mac and Im pretty sure its the same for PC.
Originally posted by:Steam itself and most Steam games are 32-bit which cannot address more than about 3 GB plus your OS. Not to be that guy, but the 4 GB limit on memory is OS dependent, not program related. As long as you are running a 64-bit OS, a 32-bit application can access more than 4 GB of total (V)RAM. So doing some more research, it appears I was wrong.
A 32-bit process will be limited to 2 GB of RAM on a 64-bit operating system, not counting VRAM. And to show I should read the entire article before editing/posting, it appears developers can work around this, but by default they will be limited in how much RAM the 32-bit program can access.