I am running both better memory Meter and FreeRAM XP Pro1.52. on my standalone installation.
Today I had related files open: a part, drawing, assembly doc.After a couple of minor part edits, save, then up pops memorymessage from hell.
Both meters were dipping fairly quickly but only hit about 42%memory available at the time of crash.
Second incident, when sectioning a model in an assembly, and bothmeters suddenly nose-dived to absolute zero and the message cameup.
At that point I gave it a boost on the latter program, set for a512MB memory boost and it read back a resulting 23% gain inavailable memory, verified on the adjacent Better meter. I thenselected the error message 'try again' button and she crashed.
Once the message comes up you are meat. The buttons should say: 'goahead make me crash' or 'I am crashing either way'.
The only other app I had open was Firefox playing a radio station.
I periodically use the feature on FreeRAM XP to purge memoryandoften reboot midday. The models are not huge nor complex, they arefluid assemblies and the drawings open up fairly quickly. I dodrawing sheets sets in nomore than three pages.
I endeavor to use good mating practices, planes and faces in thatorder of preference and construct larger models in tieredsub-assemblies.
I don't use 'undo' much, I usually choose to edit my way out ifpossible, though that can be when bad things happen.
My methods have worked for me through various releases but this onehas been particularly problematic, I am sorry to say.
The meters are not even counting the the 512 MB DDR3 in thegraphics card, as far as I know. I cannot see system memory beingthe issue here, from what I see.
Two memory meters that consistently output virtually identicalreadings that indicate some there is usually at least 1.5 gigavailable vs. a software memory leak or bottleneck.
Oh yeah, and auto-save failed me both times but that is a anotherbeef.
It seems to me that SolidWorks might have some difficulty purgingmemory compared to earlier releases.
Anyone that might have experienced this figured out a solution?
SolidworksAdministration
Today I had related files open: a part, drawing, assembly doc.After a couple of minor part edits, save, then up pops memorymessage from hell.
Both meters were dipping fairly quickly but only hit about 42%memory available at the time of crash.
Second incident, when sectioning a model in an assembly, and bothmeters suddenly nose-dived to absolute zero and the message cameup.
At that point I gave it a boost on the latter program, set for a512MB memory boost and it read back a resulting 23% gain inavailable memory, verified on the adjacent Better meter. I thenselected the error message 'try again' button and she crashed.
Once the message comes up you are meat. The buttons should say: 'goahead make me crash' or 'I am crashing either way'.
The only other app I had open was Firefox playing a radio station.
I periodically use the feature on FreeRAM XP to purge memoryandoften reboot midday. The models are not huge nor complex, they arefluid assemblies and the drawings open up fairly quickly. I dodrawing sheets sets in nomore than three pages.
I endeavor to use good mating practices, planes and faces in thatorder of preference and construct larger models in tieredsub-assemblies.
I don't use 'undo' much, I usually choose to edit my way out ifpossible, though that can be when bad things happen.
My methods have worked for me through various releases but this onehas been particularly problematic, I am sorry to say.
The meters are not even counting the the 512 MB DDR3 in thegraphics card, as far as I know. I cannot see system memory beingthe issue here, from what I see.
Two memory meters that consistently output virtually identicalreadings that indicate some there is usually at least 1.5 gigavailable vs. a software memory leak or bottleneck.
Oh yeah, and auto-save failed me both times but that is a anotherbeef.
It seems to me that SolidWorks might have some difficulty purgingmemory compared to earlier releases.
Anyone that might have experienced this figured out a solution?
SolidworksAdministration
