OS Frozen while running xNormal
I've tried to render a relaxed cone map in 2048x2048 on two of my Win 7 machines now, and I gave it up on both of them.
On my i7 930 with 12 Gigs of RAM the Rendering was at 6% after 5 hours, on my Turion dualcore laptop with 4 Gigs at 0.5% after 2 hours.... that doesn't bothers me to much, as I can let the machines run for days if needed, but both were completly frozen other than the percents going up slowly, in case of the turion laptop I couldn't even see the percentage anymore.
OS was pretty unresponsive and the mouse was frozen. It just happened that I had a Task Manager window with the performance tab open on my i7 while I ran the rendering and there I could see that only one CPU Thread was utilized heavely, and even this one was barely at 50%, and not even 4 Gigs of RAM used.
I know that while the CPU would be heavely used this sort of thing is expected, but it doesn't looks like xNormal is really using that much CPU and even if, while running things like a tiled build in world machine I never noticed such a behaviour with my Win 7 installation.
Is this problem with the unresponsive OS comming from xNormal reaching its Memory limit due to not being a 64bit Application? Is it a bug with the newest release of xNormal? Is it that 2048x2048 is just too big (though I got the same problem with 1024x1024)?
If someone could give me a hint if thats a known problem with xNormal, or if I'm doing something wrong, I would appreciate it.