SU17 Out of Memory Issue & Move/Ctrl to copy Crash
-
I've a similar Laptop and no issues so far.
Are you saving the file locally or to a network/USB drive or cloud folder?
-
Thanx Rich
All saves are Local...though many of my files are huge. The current one is 154,585kb.
I've done a Clean Install of SU17 and I still have the same issues. I've noticed that when I move/ctrl or other similar command, SU17 does a Autosave; why, I don't know. And its during this save, with the creation of the Autosave*.skp and *.tmp file that it crashes. I'm going to shut off Autosave for a bit to see if its that. Then, if not, I'll run a GPU stress test to see if its that's causing the crash. Come January the computer is 2 yrs old.
-
Just an Update to everyone.
I shut off the AutoSave feature and have not crashed since. Turned it on again for validation and voila! CRASH within 15 minutes. So definitely something is wrong with the AutoSave feature, at least on my computer.
Ran a Furmark GPU Stress Test for over 2 hours and it came back successful. No problems there.
Note to self: Remember to 'click' Save, often.
-
I have found that disable thumbnail on save results in faster saves, and in the past, resolved crashing with very large file.(thousands of component instances)
If you can live without the thumbnail as I can........Model info......file......(untick)redefine thumbnail on save.
This should at least allow you to turn autosave back on.
Charlie
-
Thank-you Charlie
I will try that
-
Resurrecting an old thread. SU2017 has been the most unstable version I've used. Always getting out of memory errors, or crashes when simply moving groups or a similarly uncomplicated command.
Anyone else? -
It has happened with me with move+rotate+copy but now simply stopped. I have 32Gb and not that complex model where it's happening, so it's not the crash.
It's related with autosave imho. I think thumbnails are no longer being saved with autosaves even if they are active with regular saves but I think when autosave happens, it's kicking in with move and rotate somehow, when it shouldn't.
-
I think you are right JQL, todays crash was a rotate/array, so during a simple copy in a model I only just started. I have 64gig, so plenty!
-
I'm still having this problem though to a lesser extent, don't know why. I've updated when SU said there was one, twice since I began this tread...maybe its that.
As I'm moving around a large model [also move/ctrl, rotate/ctrl] sometimes the monitors go Black for a second or two before they refresh. And, every-so-often it will crash during this event. Since the GPU Stress test I ran awhile back was fine I ran Memtest86 [a 4 hour memory test] and it also came back perfect. I can only conclude its SU17 that is buggy.
We'll just have to continue reporting every crash and hopefully they will fix it.
-
I've noticed that always when its crashing the autosave works. However it definetelly interferes with the geometry I was moving around.
I was moving some vertexes when I had a crash and the autosave kicked in. When I opened the autosave, the vertexes had moved some 10m and messed the model all over with some unexpected tris.
-
Just to catch up with this thread, I haven't had any issues at all since disabling Autosave. So imo it is definitely a problem with that function.
Advertisement