Can anybody answer this?
8gb memory may not be sufficient depending on what is your file size, ho large is your assembly and related things.
I have 16gb.. it does it all the time with simple parts... that is, parts I did back in 2001... I NEVER SAW THESE ERRORS.... it has gotten worse but started ~2012.
my 2 cents,.. it's called, poor memory resourcing and programming.
Do you ever close out of solidworks or restart your computer? RAM will not get fully released ever time you close a file.
Restart your computer every day to purge application from holding onto RAM.
Do not ask why, ask how to fix it
And here is how you do - Set your Windows virtual memory to:
Initial value: e.g. 12 GB
Maximum value: e.g. 12 GB
If you set the initial value to small number, you will continue getting errors. I want to say that initial value must be big enough to satisfy your need at maximum load.
If you don't know how to change the size of virtual memory, then google for it.
Never Mind. I have 16G memory and receive the same error for opening an assembly made of 71 components.
It doesn't matter how much actual RAM you have if you set your virtual memory at 256 MB
Change it to 10 GB or more and the problem will be gone
start > run > regedit
search for HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows\GDIProcessHandleQuota
change it to 20000 or so.
SolidWorks has some memory dumping bug that can be annoying sometimes. Closing out SW and restarting your computer from time to time seem to help keeping those out of sight.
That is pretty much any CAD software. When you close a file, it doesn't release 100% of the memory. Just like anything, if you keep it running forever things are bound to get wonky. I start my computer every day fresh. No worries.
That is not true. That is just poor, lazy, and unprofessional programing. How common it has become doesn't make it acceptable.
Well, there is only around 23 million lines of code in the base software, and not being a programmer I'll have to take your word that it is easy to fix. I don't believe it is easy. Also, I did not state it was acceptable, it is just what I've learned over many years of experience using CAD software and what practices help the workflow. There has been vast improvements in this area of releasing the memory over the years, but unless you can re-architect the entire structure and maintain all compatibility with everything including RAM, processors, video cards, IOS, Bios, etc. good luck.
I would submit an enhancement request.
I understand. It is a philosophy that is wide spread. As hardware becomes cheaper, faster and higher capacity... most spend less on software efficentcy. I don't think it would ever be an easy (inexpensive) fix, but it doesn't make it any less frustrating.
I have 16GB of RAM and get that message every time I start up SolidWorks in the morning after turning on my computer. This seems to have only been happening to me the last couple of years.....don't recall it happening in SW2015, but may have. Time tends to get muddy when one transitions from middle age to old fart.....
LOL, yeah I get that message sometimes too. It's something with Rx. I did ask about it once and forgot the reasoning already. I usually just ignore it (I'll only spend so much time researching...over the years you kinda get numb to certain aspects and I try to move on if I see it as a non-issue). Muddy waters for sure....hard to believe I've been using the software longer than most kids coming out of the Tech colleges have been alive....weird.
I think mine was related to not having a computer in the list. So Rx might be thinking...hey, buddy you should check on this...but it can't because they never tested this configuration? Now I have to go look at my old emails...
You may be onto something....mine is a mutt put together by an IT guy that no longer works here, so its definitely not on their list of approved systems. Like you, I just ignore it and have yet experienced any issues regarding lack of resources....
Back in the day (eye roll), I believe Windows took 1/2 of the RAM for itself regardless of what it needed.
Don't know if it's still true, I would hope Windows is more dynamic than that, but dunno.
Also, if you have a USB stick laying around not doing anything, you can use it to cheaply extend your RAM.
Search "RAMboost" (or something like that, I run this feature on my home laptop, so I'm going from memory at the moment).
Hey Kevin, yeah trying to keep up with technology is extremely difficult. I almost switched careers into IT during the time when IT was becoming a new big field, even got certified on Server 2000. Glad I did not, it can be an unappreciated job.
Back in the 32bit days, windows ate up a bunch of the RAM and was limited to 4GB (and not really 4GB either), now with 64bit and multicore processors it's a different story, but Windows still does take a fair share. RAM is cheap in respect to other things, so everyone I think should be running at least 16GB nowadays. A few computers even have the ability to dedicate a single core to an application. SOLIDWORKS can only take advantages of the multiple cores in certain situations like simulation and rendering, but does use them a few other ways.
The whole RAM question gets pretty deep too when you start looking at ECC ram vs SD or DDR ram...yikes it can get complicated and confusing very fast.
being that we are getting this same error with 32GB RAM, should this recommend 64GB? Solid works never uses more than 8GB on the systems we have observed. Could it be possible that Solidworks doesn't see all availible RAM?
Solidworks says low on resources, yet system shows 12 of 32GB in use
This is the question (How effectively RAM is used?) I'm asking myself.
Out of curiosity, are you using Windows 10?
I have been noticing that this is more common in Windows 10. In these cases, the problem can be something called "Commit Charge" which you don't see in the Task Manager. You could have ample physical memory remaining, but still run out of this resource. To see it, you need to open the Windows tool called Resource Monitor.
Type "resmon" at the run line to get to it quickly. On the memory tab, you can see the Commit Charge on the graph to the right. Once that hits 78%, you'll start seeing warnings in SOLIDWORKS. Here is the tab in the tool from my Windows 7 installation. I am using about 55% of my available commit charge.
You can also see the Commit column to find out which process(es) is/are the culprit using up all your address space. Other processes could be consuming this OS resource and leaving little left for SOLIDWORKS. Windows 10 seems to be more greedy with this resource and causing more warnings.
Of course, there are other explanations as this thread has raised. I am just adding one more possibility.
I think you need to shutdown and restart SW few times a day to release some memory built up when you manipulate//render big assembly or do some heavy calculation
by the way, you need a decent size about 16 gb nowaday to run SW
Retrieving data ...