memory leak??
memory leak??
(OP)
Hi all,
I believe we all know how SW holds onto RAM even after closing documents.
Do any of you SW/WindowsXP gurus have any way that allows users to clear RAM after a solidworks document is closed? We are on SW2009 sp3 with 2Gb RAM per our VAR recommendation. We are also waiting for the upgrades to the 64 bit systems. In the mean time depending on what we work on, crashes occur when RAM gets eaten up because SW doesnt release it. We have ProE users I understand that can clea r RAM with a couple mouse clicks when exiting documents. Why cant SW do this as well?
I believe we all know how SW holds onto RAM even after closing documents.
Do any of you SW/WindowsXP gurus have any way that allows users to clear RAM after a solidworks document is closed? We are on SW2009 sp3 with 2Gb RAM per our VAR recommendation. We are also waiting for the upgrades to the 64 bit systems. In the mean time depending on what we work on, crashes occur when RAM gets eaten up because SW doesnt release it. We have ProE users I understand that can clea r RAM with a couple mouse clicks when exiting documents. Why cant SW do this as well?






RE: memory leak??
I run a bat file when I start having troubles. I did not write this, just modified it.
CODE
rem 10/2/06 - JJR - created: TaskKill with force the solidworks process and its assoc. process tree. <end>
rem 10/27/06 -JJR - modified: TaskKill licensing stuff from release builds too, this takes care of the journal file message when restarting release builds quickly after killing the sw process. <end>
rem flag usage: /f (forcefully terminate), /im (the image name of the process), /t (terminate entire process tree) <end>
taskkill /f /im sldworks.exe /t
taskkill /f /im solidworkslicensing.exe /t
taskkill /f /im solidworkslictemp.0001 /t
taskkill /f /im solidworksexplorer.exe /t
taskkill /f /im solidworksexplorer.exe *32 /t
taskkill /f /im SolidWorksLicensiong.exe *32 /t
taskkill /f /im SolidWorksLicTemp.0001 *32 /t
taskkill /f /im taskeng.exe /t
rem START /MIN C:\DST_SolidWorks\Executables\StartSolidworksExplorer
START /MIN C:\DST_SolidWorks\Executables\StartSolidWorks2009
Standing
SolidWorks Pro 2009 x64, SP3.0, PDMWorks Workgroup, SolidWorks BOM,
HP xw8600, 64-bit Windows Vista Business, Service Pack 1
Intel Xeon CPU, 3.00 GHz, 16 GB RAM, Virtual memory 166682 MB, nVidia Quadro FX 4600
RE: memory leak??
RE: memory leak??
TOP
CSWP, BSSE
www.engtran.com www.niswug.org
"Node news is good news."
RE: memory leak??
RE: memory leak??
"Art without engineering is dreaming; Engineering without art is calculating."
Have you read FAQ731-376: Eng-Tips.com Forum Policies to make the best use of these Forums?
RE: memory leak??
Does this batch just clear RAM and keep SW open?
Note to all, I want to stay in Solidworks and clear RAM after exiting document not exit out entirely. Thanks
RE: memory leak??
It closes SolidWorks and others in the list.
Standing
SolidWorks Pro 2009 x64, SP3.0, PDMWorks Workgroup, SolidWorks BOM,
HP xw8600, 64-bit Windows Vista Business, Service Pack 1
Intel Xeon CPU, 3.00 GHz, 16 GB RAM, Virtual memory 166682 MB, nVidia Quadro FX 4600
RE: memory leak??
Try running a memory utility like http:
RE: memory leak??
RE: memory leak??
Look in API help for how to do this. It isn't hard.
TOP
CSWP, BSSE
www.engtran.com www.niswug.org
"Node news is good news."
RE: memory leak??
Clearly, SW _does_ have memory management problems.
Not that XP is any damn prizewinner.
I may try that batch file, but so far, the only reliable remedy I've found is a reboot. .. typically twice a day, sometimes many more.
Mike Halloran
Pembroke Pines, FL, USA
RE: memory leak??
http:
http://fi
Don't know if they will help, but setting up the performance monitor correctly will help you understand if SW is using up all your memory.
Regards,
Scott Baugh, CSWP![[pc2] pc2](https://www.tipmaster.com/images/pc2.gif)
FAQ731-376: Eng-Tips.com Forum Policieswww.scottjbaugh.com
RE: memory leak??
RE: memory leak??
discussion on cache clearing
TOP
CSWP, BSSE
www.engtran.com www.niswug.org
"Node news is good news."