Just realize the screenshot are compressed and can't be viewed.
Let's move this to a less disruptive forum: https://www.cadforum.net/viewtopic.php?f=3&t=450
Users had reported RX complaining low memory even with 32GB RAM install.
How could SW see low memory before any file is opened?
Changing Windows swap file to fixed 64GB will remove that.
While working on a STEP import with 1000 part SW crashed will low memory. With 6GB free RAM.
This is a recreate of what happened. I can repeat this with different large STEP files. So feel free to test it yourself.
Very simple steps.
Import STEP, break link, Save Body, Create Assembly. Turn Off "Derive resulting parts from similar bodies" for maximum effect. I have it on for a quick example.
Watch Committed grow. My highest was 77GB. My pagefiles size is 64GB + 64GB.
Start with SW fresh start, 14GB committed, 7.3GB free RAM
SW used 253MB Private Byte 396MB Working Set
After Save Body, 44GB committed, 5.3GB free RAM.
SW used 12GB Private Byte 3GB Working Set
Committed increase 44 - 14 = 30GB SW used 12+3 = 15GB RAM used 7.3-5.3 = 2GB
Extra in committed 30-15-2 = 13GB (not sure if committed include RAM used, assuming it is)
Close all open files in SW, 43GB committed, 6.2GB free RAM
We free 1GB RAM and 1GB committed. So committed include RAM
SW will not free the committed until it's closed.
Since closing SW release all committed, they are allocated by SW
Reopen SW, back to where we started. So it is not a problem with other running program.
I also observed committed grow slowly during the day with every file opened. Closing the files does not recover all committed memory.
That's why user need to restart SW.
I believe this had been around for a long time. Someone go find out why and get it fix.
If anyone has same problem, please reply and add to the case.
We might be able to gather enough for a case :p

@AV
Nice research!
It's kind of sad to see that you had to go through this ammount of effort to hopefully get them to understand, admit and eventually correct a long lasting issue.
I sincerely hope that they give you what you deserve for going through all of this albeit them completely ignoring all the leads that were given to them.
Since they have ignore it for years, I don't think anything will happen.
And that's all I want to prove.
The word they love to use, disruptive.
Like everything else, this will sink to the bottom of SwYmP and forgotten
Well, now that it's created, we can always "transfer" it on a daily basis to keep it at the top.
Wink wink
Might wanna save this post in a Word file in case they delete or move the thread to a private area.
Add to wiki again? LOL
1) Do you stop all of the unnecessary SW add-ins before starting the import?
2) Do you restart SW fresh before starting the import so that any DLLs that got loaded for previous tasks aren't running?
3) Do you stop/end task all unnecessary autostarts loaded into Win10 before starting the import?
4) Have you researched your Win10 memory usage/setup independent of SW?
5) Do you have a 32GB (or so) USB stick laying around just filling a drawer that could be used for ReadyBoost? (assuming you're not on an SSD)
@KC LOL
Read the post and look at the Screenshot.
And no, I'm not use certified graphic card or driver.
ReadyBoost? Really? Do you know how it work?
I have 64GB swap on SSD and another 64GB on HDD.
I'll try RAM Doubler
@KC
I believe RAM Doubler will work.
https://tidbits.com/2019/01/24/25-years-ago-in-tidbits-ram-doubler-debuts/
I just opened a 58MB STEP file with 673 solid bodies. On performing the Save Bodies, the committed memory for SW never went above 5.8GB. After closing all files, it dropped to 4.7GB. A freshly started SW sits with about 1.8GB committed. So just the process of saving a lot of bodies doesn't seem to be the problem. There is more going on here.
How big is the STEP file you are starting with?
FYI: You can see per process memory usage using https://docs.microsoft.com/en-us/sysinternals/downloads/vmmap
The one shown here 20MB x_t
SW process show much smaller committed then total committed from Windows.
The extra only released after SW is closed.
SwYmP safe screenshot
You can see SW used 12GB, Windows committed 43GB.
When SW start, its 13GB total committed.
With one part and drawing open.
@JS Thanks for VMMap
A simple open and close the same assembly repeatedly and refresh VMMap will show increasing committed from SW.
Also VMMap show Windows see all committed memory from SW, the whole 43GB. Nothing is missing, SW is accountable for all of it.
Hi @FL,
Our support and development teams have taken a look at various models and tried to simulate what you might be seeing on your end. We do see an increase in memory usage for models that contain a large number of bodies/components, but to some degree that is expected, and we can't get anywhere near the numbers you're seeing.
Would you be able to open a support ticket so we can work more directly with you and work with your model data?
Thanks,
John
The most gain in commit came from "Save Body" of an 1000 bodies import.
Which I let it run overnight.
After saving all the parts in assembly, open and close the same assembly with result in commit growing slowly.
@#$% shift enter
Yes, the Shift+Enter has gotten me a few times... you can go back and edit your comment. I do know that we are planning to update this "Enter" key behavior in the coming weeks!
Yes, I was editing and pressed enter again
Won't be able to work on this for a week or 2 or more.
Hi @FL, OK understood. If you get the spare time to open a ticket and share the model that would be great.
Thanks,
John
Same Problem on importing and Save an IFC
@FL
The best experience we got is if we deactivate Windows "Fast startup". After every Crash of an App, it seems windows get Problem using the all RAM he has. Because of that, we deactivate Windows "Fast startup" on all Computer we install SolidWorks. The RAM behavior is way better if user “Shutdown” and purge RAM instead reuse old RAM-Content on every Windows start.
For user with a High Ram Usage we recommend them to Restart Computer if SolidWorks Crash on a High RAM Work. e.g. on Import Huge IFC files.
The low memory warning from SW got nothing to do with RAM.
It is pagefile.
Since Windows adjust it when need, it's always "full". SW see that and keep complaining.
Set a large Pagefile size "fix" the problem until Windows use it up.
The problem on STEP import also was not RAM, it's pagefile.
Contain of STEP got swap out to pagefile which is correct but pagefile need to be big enough to hold everything for the STEP.
Which user have no idea how much is needed until it crash.
Don't know if I let Windows manage Pagefile will fix that problem.
Reason for a fixed pagefile size was to reduce file fragmentation, slow access, no space on drive for pagefile and SW complaining.
SSD might remove first 2 problem.
Space probably not a problem. Drive are pretty big now.
SW, we can ignore the warning.
Not using SW now so can't test it.
SOLIDWORKS User Enhancement Idea
The freeing of memory on document close has been implemented in SolidWorks 2025 SP2. SolidWorks will no longer wait for the operating system to free or reuse the memory and you should now see the Working Set reduced after file close.