MM 3.3 crashing

[Anonymous]

Thanks to help in my earlier post I have got MM 3.3 running, with basic rendering only though due to limited graphics on laptop. When I open an object and start to work MM crashes after a minute or two. Is it possible the autosave function is causing this and is it possible to disable it? 

Are there any other things I can try?

Regards

[Anonymous]

Do the crashes happen too if you don't do anything on the object? If yes, this would point to autosaving as the bad guy.

I don't know a way to disable autosaving completely.

But you can set the time interval of the saves to a very long time:

In meshmixer.ini (while MM is down) search for the line

AutoSaveIntervalSeconds=60

This means MM will save each minute (default).

AutoSaveIntervalSeconds=3600

would save each hour...

In case you do this make sure to save frequently by hand.

-----

Do the crashes happen on default objects (as the bunny) too, or on special imported ones?

How much RAM is available? 

[Anonymous]

Thanks for taking the time to respond.

I have changed the line in .ini to =3600 and saved it but notice it reverts to =0 after each restart.

MM does not crash, well for 5 minutes I waited if I open the program but not load anything.

It does crash after a few minutes if I load the Sphere, even just leaving it.

At the crash I get a message 'Uh-oh I'm sorry to tell you this but MM has crashed ------ etc.'

On reloading MM I do get the message that it had crashed and I could reload the object etc.

I have 4 MB of Ram, I realize this may not be enough.

Regards 

[Anonymous]

Are you sure about the 4 MB RAM? Shouldn't it be 4GB?

Hmm 3600 works and doesn't turn to 0 here on MAC. Maybe there's a limit on a WIN version. Try to increase the default 60 in several steps.

MM reads the ini at start, keeps its values in mind and writes those values back to the ini when you quit the app. So editing the ini makes sense only when MM isn't running.

[Anonymous]

Thanks

You are correct it is 4Gb. You may also be correct regarding aurosave so I have removed the autosave instructions in .ini completely doing this after MM was closed. After loading the program only ran for a few minutes with sphere loaded again and then crashed.

I checked .ini afterwards and it still does not have the autosave lines.

[Anonymous]

If you remove this line MM writes autosave files with the default interval of 60 sec. Just tried that.

4GB aren't that much memory nowadays but still fit to the minimal system requirements and shouldn't be a crash causing issue if there are not that big projects (as a sphere) loaded in MM.

Are there some third party programs running in the background doing certain routines in certain intervals? Try to close as much tasks as possible (temporarily) to check if there might be a conflict...

[Anonymous]

I have ensured there are NO other programs running at the same time. or at least none that show up in Task Manager. This is because I installed MM after a clean installation of W7, my idea is to use this laptop just for 3D printing and so I want to get MM working first.

I have been back into .ini and started the autosave interval at 1000 and will work up as much as it will allow.

I will report further.

[Anonymous]

Further update. I found old versions of MM program and so chose version 2.9 from 2015. So far this has been running and working even with my poor graphics to add supports to a model for perhaps 1 hour. I guess other, later versions will work but I may not risk trying them.