Having been told by various sources that 32-bit Windoze just won’t cut it anymore (can’t allocate enough memory to Blender, it seems), I installed Ubuntu 10.04 using Wubi so I have dual-boot options. My processor is a dual-core AMD-64 so Wubi installed a 64-bit capable version of Ubuntu.
After Linux 64-bit Blender finally got the off the MIA list, I d/l’d it today and booted up Ubuntu and tried a rendering, a scene that without fail caused Blender to crash of memory starvation under Win32. No crash! Yay! Looks like 64-bit Linux saved my bacon.
However, after the rendering finished, using either F3 or the Save As… menu item consistently crashed Blender. Great, now I can render but not save. Still screwed.
After cussing a bit, I recalled statements that some rendering problems can be worked-around with a little voodoo, namely rendering to a new window. So after the rendering (not to a new window) was finished. I opened the image in a new window and tried saving from that and then the save was successful. Cool. Workarounds are fine by me as long as they actually work.
So next I set Blender up to render directly to a new window. So, sad… Blender not only crashed :(, it took Ubuntu with it, total system lockup, power down required. Damn!
So, is this common behavior for Blender 2.55 64-bit under Ubuntu? The crashes under Windoze were always memory-related as far as I could tell. This seems quite a bit different. Any Linux/Ubuntu gurus have any insights or recommendations?
Thanks!