
There are reasons why this number will be something silly like 8-10GB when only 100-500MB is actually allocated and in use. Xcode is one of the most VM heavy apps I use, and it is using about 23GB of VM address space on my Big Sur machine. What the OS reports for process VM is the usage, not the upper limit. Back in the 32-bit days, I've worked on projects where we exhausted the whole 4GB VM address range because of the abundance of memory mapped files and crashed apps doing that. But the whole executable exists in the virtual address space at all times.įor some reason I can't fathom, Apple does this with fonts as well.

Helps a lot when dealing with large apps like Lightroom or Office, only loading the code for bits that are needed as it goes. The operating system will memory map executables as a way to lazily load the code to execute. Once I try to read a page from that file, it gets loaded into RAM, though. If I have a 2GB file, and I map it into memory, it's given virtual addresses that take up 2GB. Memory mapped files are a common example. They tend to be correlated, but there are plenty of things that will impact virtual memory usage without impacting real memory usage. Real memory is what's actively required by the process at that moment in time. Virtual memory usage represents the addresses in use by a process. Virtual memory as a feature does provide for a lot addresses that a process can use for things. Specs are 16" MBP M1 Max w 64 Gb ram - 4 TB SSD - MacOs 12.0.1 and LRC Version 11.0 - Screen attached - LG HDR 4K Display LG 32UN880 32'' 4K Ergo IPS Monitor How can viewing a 7 gb image cause a machine like this to run out of memory?

Not sure if Adobe have some work to do with LRC or 4 days is not long enough for all new Mac background tasks. No standard 1:1 preview was built in LRC but still I would have expected it to handle it especially considering the capabilities of this machine. Only other apps open was mail / canary mail / safari / messages / App Store and activity monitor

It was a large pano 6.37 gb in psb format. I didn't think this would happen like ever. THANK YOU TO for pointing out a 445.42 GB memory leak - Anyone know how to figure out what caused it so I can try and get the issue reported / fixed?īrowsing + Zooming in and out of a large Pano in Adobe Lightroom Classic today and already had the system run out of memory.
