Add RAM won't solve SW out of memory problem.
Increase pagefile size will.
I got this while saving bodies out of an import file with 1000 bodies:
So I start another import (500 bodies) and watch memory use:
Committed go up slowly and I let it run overnight.
It didn't crash and total committed is 58GB with SW 18GB.
So something asked Windows for 58GB which most of it is SW because it went down when SW is closed.
Committed doesn't mean used. It means Windows allocated "memory address" for that program, or reserved memory.
Total allowable "committed" is RAM + pagefile.
You can see I have 80GB = 16GB RAM + 64GB pagefile
Since SW process only show 18GB committed with 6GB RAM free, I'll say SW keep asking for RAM which it never used.
I'll say the out of memory earlier was because SW asked for more then 80GB and Windows told it no.
Instead of releasing what it allocated and didn't use, it shut itself down.
I'll run the 1000 bodies again tonight. I've add another 64GB to pagefile on another HD.
144GB on the last screenshot. SW didn't release anything even I went and change pagefile size in Windows
Let see how it looks tomorrow.
This is for my recommendation of having a large enough pagefile so SW won't crash.
The usual recommendation was 4x RAM. Some even turn it off believing 16GB or 32GB RAM is enough.
They're correct since SW only has a 3GB working set but asked for over 40GB from Windows.
This also explain why adding RAM won't resolve "running out of memory".
If you want an headache, read this:
https://superuser.com/questions/1174229 ... windows-10
The most important part:
When commit charge fills up and windows starts asking me to close things, most of the time physical memory is at around 60%. This seems horribly inefficient.
It isn't that Windows is being inefficient. It's the apps you're running. They're committing a lot more v.a.s. than they're actually using.
