Dan, I'm not sure this report can help in some way, but I tried produce the crash reported and I noticed that it happened after Smooth computation has been done and when starting the Soft process (maybe about 10%) - in accord with Information line.
The PC I used have 4GB, Intel HD Graphics (i5), Windows 7 64Bits.
I needed smooth the initial cube 8 times and then call smooth (393,216 polys):
In the first stage, wer.erl took ~2,100,000MB of memory until smooth was done, falling to ~1,400,000 with a small increase until I got the crash.
It was generated a erl_crash.dump in the Wings3D.exe directory (I do not use the "Programs Files").
The header refers the crash as memory allocation problem:
The PC I used have 4GB, Intel HD Graphics (i5), Windows 7 64Bits.
I needed smooth the initial cube 8 times and then call smooth (393,216 polys):
In the first stage, wer.erl took ~2,100,000MB of memory until smooth was done, falling to ~1,400,000 with a small increase until I got the crash.
It was generated a erl_crash.dump in the Wings3D.exe directory (I do not use the "Programs Files").
The header refers the crash as memory allocation problem:
Quote:=erl_crash_dump:0.2basically the same problem we had talk about in the past in the old forum.
Sun Nov 03 01:23:12 2013
Slogan: eheap_alloc: Cannot allocate 1898305688 bytes of memory (of type "heap").
System version: Erlang R16B02 (erts-5.10.3) [64-bit] [smp:4:4] [async-threads:10]
Compiled: Mon Sep 16 19:28:19 2013