AnsweredAssumed Answered

Purge undo

Question asked by Craig Deroche on Apr 6, 2008
Latest reply on Apr 20, 2008 by Mauricio Martinez-Saez

Like • Show 0 Likes0
Comment • 4

Does anyone know if there is a way to purge the undo cahe without exiting SW? I am working with a rather large surface model and every time I trim, extend offset etc. my memory use goes up a little bit more. I am guesiing it's because of the information stored in the undo. After a while I have to exit out of SW and open the file again. When I do that my RAM ussage drops back to a resonable level. If I don't, after a while I run out of RAM and the system locks up.

I am still working on an old single core P4 with 2 gigs of RAM. I just ordered a new T3400 with the E8500 CPU. I am hoping this problem goes away with that but until I get it any suggestions would be great.

Thanks,

Craig

No one else has this question

Outcomes

Aaron Hayden Apr 14, 2008 12:10 AM

Craig,

I have been noticing something similar. I have an assy with surfaces that uses about 2 gig of ram. Windoze reports 3.25 gigs total and with SW using 2 there is about .5 gig left available with everthing else that is also running at the time. SW will slowly start eating that .5 gig until it slows way down and finally crashes. I've learned to restart SW once it starts to slow, but it's lost time waiting for this assy to re-load. Here's the kicker, if I just save and close my assembly SW will often still have a gig of memory used up. However, if I close out SW all together and start a new one it only uses something like a quarter gig. So, my theory is that somewhere between Windoze and SW memory isn't being released when it should be.

Aaron

SW 2007 SP5.0 Hotfix: #402887
XP Pro 32
Core Duo @ 2.66 gigs, 3.25 gigs ram

Actions

Michael Beem Apr 14, 2008 10:28 AM

Craig,

There is a macro command for clearing the undo list. Look under API Help for ClearUndoList

The macro would look like this:

Dim swApp As Object
Dim Part As Object

Sub main()

Set swApp = Application.SldWorks

Set Part = swApp.ActiveDoc

Part.ClearUndoList

End Sub

Actions

Craig Deroche @ Michael Beem on Apr 14, 2008 2:33 PM

Thanks Michael, I'll check it out.

Craig

Actions

Mauricio Martinez-Saez @ Craig Deroche on Apr 20, 2008 9:09 AM

Clearing the Undo List will not remediate the problem with SW deficiencies in memory management... SW likes to keep the memory... he does not release the memory when you close an assembly... only when you close the application and even so it takes some time to do that.

And once it gets near 3GB of memory utilization (on Windows x64 with 16GB of RAM on the machine) the performance degrades to a point that the machine looks like it is lock-up (however sometimes whct happen is that the system cache is very small (for some reason SW gets all the memory out of the system cache.

Actions

4 Replies

Aaron Hayden Apr 14, 2008 12:10 AM
Mark Correct
Correct Answer
Craig,

I have been noticing something similar. I have an assy with surfaces that uses about 2 gig of ram. Windoze reports 3.25 gigs total and with SW using 2 there is about .5 gig left available with everthing else that is also running at the time. SW will slowly start eating that .5 gig until it slows way down and finally crashes. I've learned to restart SW once it starts to slow, but it's lost time waiting for this assy to re-load. Here's the kicker, if I just save and close my assembly SW will often still have a gig of memory used up. However, if I close out SW all together and start a new one it only uses something like a quarter gig. So, my theory is that somewhere between Windoze and SW memory isn't being released when it should be.

Aaron

SW 2007 SP5.0 Hotfix: #402887
XP Pro 32
Core Duo @ 2.66 gigs, 3.25 gigs ram
Like • Show 0 Likes0
Actions
Michael Beem Apr 14, 2008 10:28 AM
Mark Correct
Correct Answer
Craig,

There is a macro command for clearing the undo list. Look under API Help for ClearUndoList

The macro would look like this:

Dim swApp As Object
Dim Part As Object

Sub main()

Set swApp = Application.SldWorks

Set Part = swApp.ActiveDoc

Part.ClearUndoList

End Sub
Like • Show 0 Likes0
Actions
- Craig Deroche @ Michael Beem on Apr 14, 2008 2:33 PM
  Mark Correct
  Correct Answer
  Thanks Michael, I'll check it out.
  
  Craig
  Like • Show 0 Likes0
  Actions
  - Mauricio Martinez-Saez @ Craig Deroche on Apr 20, 2008 9:09 AM
    Mark Correct
    Correct Answer
    Clearing the Undo List will not remediate the problem with SW deficiencies in memory management... SW likes to keep the memory... he does not release the memory when you close an assembly... only when you close the application and even so it takes some time to do that.
    
    And once it gets near 3GB of memory utilization (on Windows x64 with 16GB of RAM on the machine) the performance degrades to a point that the machine looks like it is lock-up (however sometimes whct happen is that the system cache is very small (for some reason SW gets all the memory out of the system cache.
    Like • Show 0 Likes0
    Actions

Purge undo

Outcomes

Related Content

Recommended Content