Warning: SOLIDWORKS System Resources Running Low
This blog is for those unlucky individuals working in SOLIDWORKS are persistently annoyed by this message.
You check the Task Manager, only to find that there are still plenty of RAM left; not even at 50% capacity. Most of the time, you are likely to ignore or dismiss this message and just continue working. However, if this message turns into “Available system memory is Critically Low” then we are at a risk of the application crashing.
In this article, couple of suggestions will be made which will help prevent these messages from appearing, and hopefully avoid the inevitable crashes due to insufficient system memory. The resource monitor does not pin point what’s causing the lack of memory/resource. It could be any of or combination of GDI Objects, RAM and VRAM shortage.
1. GDI Objects Limit
GDI Objects (Graphics Device Interface) is a core windows component responsible for representing graphical objects and outputting them to devices such as printers or monitors.
For every window or application that is open, it uses up GDI Objects. The problem arises when there are too many objects are in use and causes unresponsive program behavior. This is also what may trigger the lack of system resources. For Windows 8 and later, the system wide GDI Objects are limited to max out at 65,536; and the maximum single process is 16,384.
The default limit set by Windows for any single process is 10,000 GDI objects. If your application GDI Objects exceeds this amount, that process is likely to crash.
SOLIDWORKS should not require more than the default limit of 10,000. If you observe over 10,000 GDI objects after following the below steps to monitor GDI usage, contact your local Value Added Reseller (VAR) for assistance troubleshooting this and reporting to SOLIDWORKS Support.
You can monitor this through the Task Manager.
This solution will involve editing the Windows Registry.
Disclaimer: Modifying the registry can cause serious problems that may require you to reinstall your operating system. We cannot guarantee that problems resulting from modifications to the registry can be solved. Use the information provided at your own risk.
As mentioned before, the windows by default sets the GDI Objects limit for a single process to be 10,000. However the maximum allowed is 16,384. By increasing this limit in the registry, it will give any given application more room to breathe.
2. Virtual Memory
Another major cause for insufficient system memory could be due to virtual memory of Windows.
Virtual memory, also known as Page File is a memory combination of RAM and a portion of your hard drive disk. Whenever your system runs out of physical RAM, Windows will make use of the Page File to temporarily store files and swap back to the physical RAM when it is freed.
By default, your virtual memory (page file) managed by windows. Custom Size allows you to set the size of the page file. As a general guide, the maximum size of the paging file should be 2 times the amount of physical RAM installed on the machine.
How to set custom sized virtual memory:
Categories: Administration, SOLIDWORKS, Support, Tips & Tricks, Usability