golem

[hieveryone]

Second try, sculpted out from a sphere. I don't really know what this thing is, I started sculpting with no symmetry and no plan at all. The program crashed countless times, mainly while I was sculpting, and I reached the million of polygons. I didn't bother to manage the polycount just for the sake of research, so this model as you see it is 1.8 million polygons (I could have done it with less than a half maintaining almost all details). As I said the most frequent crashes happened while I was sculpting, four or five times the program freezed and three times it crashed while saving. Because it also happened with the last save, I lost the details and some of the branches you can see in this image, so this is the only proof I have that I did them.
Anyway I'm attaching the logs with two examples, one is for crash while saving and the other for crash while sculpting.

[omid3098]

this is really good!

[RMS]

augh...meshmixer sucks! Nice sculpt though, amazed that you can do that with my software =)

I will need to put in some more logging to figure out these crashes. Do you have any idea which brush you were using when the brushing crashed?

[RMS]

also, I should have autosave going within a few days. That should at least mean you don't lose as much work...

(crash during save is so weird. I really can't figure that one out...)

[hieveryone]

Actually I forgot to copy the log after the crashes, and I realized too late that the program overwrites it every time. That's why I didn't attached more log files, sorry. I'm quite sure I was using the brush d1 anyway. Otherwise it could have been the move or the smooth (with shift); I can't really say for sure, sorry.
BTW thanks for working on the autosave function, sometimes it can be a life saver.
As for the crash while saving I tried to add some details on the same model on win 7 x64 and it have been able to save the project. It can be just a coincidence or maybe there is another reason, but I'm wondering if it can be a ram problem or something like that (as I already pointed out in the wish list thread I'm working on win XP 32bit).

[RMS]

I think it is definitely a RAM problem. 2 million triangles is going to need about a gig of ram, and with undo, inevitable memory leakage, etc, it is going to already be getting very close to the 2GB memory limit (which is closer to 1.7 with all the memory needed for DLLs, etc)

I think this is why you are seeing the crashes while saving. The OBJ output allocates some large internal buffers to deal with writing out quad meshes (which aren't used for writing out tri meshes, but they are still being created!). So, it is highly likely that it just ran out of memory. Did you see the "sorry meshmixer has crashed dialog?" when this happened? If not, that is the most likely cause...this could also have been the source of your brushing crashes.

You might want to try reducing triangles once in a while. There is a tutorial video here: http://www.youtube.com/watch?v=1w9wPa4xGa4

I'm going to post a link for you guys tonight to a testing build w/ autosave. So, that should make your life better =). Also this version will have open/save for a binary file format, so you'll be able to save frequently without having to generate an OBJ each time.

[hieveryone]

As I said, at the time I didn't care about the poly count just for test purpose, I expected that lack of ram could be the reason of my crashes, especially after you pointed that possibility out on the wish list thread. Thanks for the link to the reduce tutorial, I think I got how things work but it can come in handy anyway.
I certainly got the error message many times and the last save for golem was one of them (that's funny but, now that you mention it, I think I saved an image of the last error message. Next time I'm gonna post it), but I cant't say for sure if I got it every time the program crashed.
Anyway I will try and test the x64 version too, just to see if the problem comes out again with that.

[hieveryone]

Here's the image I was referring to: crashing while saving.

[RMS]

yea, that is most likely an out-of-memory crash.