crash with snapshot & 1.5.1 when smoothing

[quadf]

I do this sometimes to figure out what the smoothed objects looks like and then go back to the original object I'm working on.

by using the opencl option instead of truely smooth the object should work better for this case.
Just to know, how many memory your system has?
With the last snapshot I could smooth 9x until call smooth preview and crash ere.exe. But, I started with only 1.4GB used by other process and then it tried to break my 4GB limit and stoped to response when erl.exe was using 2.7GB.

I've just smoothed a cube up to 6144 polygons and it crashed. It was using 123 MB of RAM when it crashed. I think 16 GB of RAM shouldn't be causing problems.

[Stem]

ok guys you got to give me something more to work on here,

I was not even going to post a bug report due to lack of info I had. I only posted to show I was seeing the same problem as OP.

smoothing a cube almost always crashed after 7 times now it doesn't, until I ran out of memory.

It was looking unpredictable to me, as sometimes it would crash attempting sub-d level of 6, sometimes not.

What do you do, and in what display mode?

Default display mode.

It looks like the problem (for me) is that I am pressing the "S"(sub-d) too fast for this version of wings. If I press slowly, no problem, but if I press(repeat) "S" again too quickly while sub-d, wings does crash on attempting 6th sub-d level of a cube.
[ What I mean is:- open new scene. Create/select cube. Press "S" 6 times quickly. Wings 1.5.1 will crash(on my setup) ]

That is not a problem in 1.4.1 (stable).

[dgud]

Even with the newest snapshot?

And btw thanks for helping out with debugging this.
I really appreciate the even tough it is frustrating, don't want to spend my Saturday nights debugging wings.

[Stem]

Even with the newest snapshot?

I am using the version you posted the link to on this thread.

It is repeatable using the steps I mentioned above.
It does appear more stable apart from that, as before it was crashing during inflate. [ <- I spoke too soon. Just crashed while using inflate. The crash is now always due to faulting module nvoglv64.dll I will look at some other drivers.]

As there is no dump created, I can only give you the info I see from windows error (pic attached).

I take it this is a problem just with nVidia? I do have an AMD 7850, so I can put that in and check if needed?

Just to add:-
If I sub_d slowly, [leave a few seconds between each sub-d], then as I mentioned, not a problem. I have just sub-d a cube 11 times, giving 6,291,456 polygons (using 9.4 GB of memory). Not that I would actually do that normally LOL.(as it does get unresponsive)

[dgud]

It seems that nvidia is more sensible, all of us in the thread have nvidia cards.
On my sons computer with a amd 7850 I could not reproduce it, and neither on laptop (intel) or at work with linux amd..

[Stem]

I was trying to see what wings/erl was doing during crash, and found a crash dump is actually being created.

ah, never mind, that is the windows dump file.

[dgud]

Guys I think I messed up, can you try the new version..
Same place, my dropbox now, with a proper version, which I didn't understand why it
was not generated last time..
Note to self, do not make releases (even snapshots) after a half a battle of red wine,
on Saturday nights..trying to move code between two computers..

[Stem]

..............can you try the new version..

On first quick tests, looking very good.
I have a model to make, so will use this version for that. I will let you know later if all OK.

Many thanks for taking the time to fix the problem.

[dgud]

Thanks. That's what I wanted to hear, and sorry for the troubles.

Maybe I should start celebrating after making the release not before...:-)

[Stem]

Quick update.

Been using wings for several hours over several sessions, no crashing.

Many thanks again for fixing this issue.

Regards,

-Steve