memory leak?? 1

[swforge]

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?

 

[Standing]

swforge,
I run a bat file when I start having troubles. I did not write this, just modified it.

Rem Kill_SW_Restart.bat

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

 

[NomLaser]

Just go into Task Manager and end any SW tasks if you start having problems, assuming that you already have SW closed. Otherwise just save and exit SW then check TM to make sure that SW fully exits before starting a new session.

 

[kellnerp]

I don't think this is necessarily a memory leak. You can check on and close hidden documents through the API. This is important if you want to make sure you are referencing the right part if you use duplicate filenames.

TOP
CSWP, BSSE

http://www.engtran.com

http://www.niswug.org

"Node news is good news."

 

[NomLaser]

Also 2gig of ram may not be enough on your systems. 8GB is typical now along with 64-bit OS's. Make sure that your virtual memory is set high enough as well as this can greatly increase speed on many levels.

 

[MadMango]

Even if you run a 64-bit OS, your motherboards may not be able to utilize the full 8GB... check your motherboard and use as much as it can support. 2GB is like the bare minimum.

"Art without engineering is dreaming; Engineering without art is calculating."

Have you read faq731-376 to make the best use of these Forums?

 

[swforge]

Standing,
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

 

[Standing]

I really do not know if this batch clears any RAM.
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

 

[CorBlimeyLimey]

No, that BAT file completely kills all SW processes and then re-starts SW.

Try running a memory utility like

http://www.mkn-software.de/en/software/desktop/memmon/?page=index

 

[CorBlimeyLimey]

Do a Google search for memory cleaner or memory optimizer for oodles of choices.

 

[kellnerp]

First go into the SW API and make sure you close all hidden documents. In SW you can open a document but not have it visible. If that doesn't do it, then and only then mess with the memory utilities.

Look in API help for how to do this. It isn't hard.

TOP
CSWP, BSSE

http://www.engtran.com

http://www.niswug.org

"Node news is good news."

 

[MikeHalloran]

SW2009.5.0 XP32 4Gb /3Gb userva=2900

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

 

[SBaugh]

Here are 2 blogs I posted when I worked for Fisher Unitech this year on memory:

http://fisherunitech.blogspot.com/2009/03/how-to-prevent-memory-errors-using-4gb.html

http://fisherunitech.blogspot.com/2009/03/how-to-setup-performance-monitor.html

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

http://www.scottjbaugh.com

"If it's not broke, Don't fix it!"

faq731-376

 

[swforge]

reboot seems like the fix. I asked for some more memory as well. THANKS TO ALL

 

[kellnerp]

There is another thing at play here that you may not realize. When you use XP it allocates memory for disk cache. This is not the cache used to make virtual RAM, but for the immediate needs of the hard drive. This is why SW and various features will load faster the second time around. This cache is also used for holding part files. This cache can grow and interfere with the needs of SW for memory. And this cache is cleaned out only by a reboot.

discussion on cache clearing



TOP
CSWP, BSSE

http://www.engtran.com

http://www.niswug.org

"Node news is good news."