This MUST be 3.2, because the bug was filed with hugin 2009.2 which was released before enblend 4.0 came out.
It seems to me that this is either an imagecache bug which we know is buggy, or it's trying to blend too large an image for a 32bit machine. The alloc that fails is reasonable in the context of the stitch that is going on. At 16k x 8k pixels, we have 128M pixels. At 4 bytes per pixel, we have 512Mbytes of memory. And if you need to allocate a few images, like source1, source2, destination, you quickly run out of addressing space on a 32bit machine.... ** Project changed: hugin => enblend -- You received this bug notification because you are a member of Hugin Bug Hunters, which is subscribed to Enblend. https://bugs.launchpad.net/bugs/679390 Title: enblend St9bad_alloc [out of memory] when trying to render Status in Enblend: Triaged Bug description: Odd, this: using Hugin 2009.02 [RC1, current for download] on Mac OS X. I'm trying to render a 37-frame equirectangular pano which I have successfully rendered before but came back to in order to tweak the exposure settings. Other than new exposure settings, nothing is different from the previous attempt to render with the same version of all tools as I have now. Log file attached. _______________________________________________ Mailing list: https://launchpad.net/~hugin-bug-hunters Post to : [email protected] Unsubscribe : https://launchpad.net/~hugin-bug-hunters More help : https://help.launchpad.net/ListHelp
