enblend St9bad_alloc [out of memory] when trying to render

Bug #679390 reported by dexotaku on 2009-12-12
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Enblend
Undecided
Unassigned

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.

dexotaku (dexotaku-users) wrote :

The file hugin error log.txt was added: Hugin error log

dexotaku (dexotaku-users) wrote :

..and yes, I know I'm using --fine-mask; I got those black lines without it.

Yuv (yuv) wrote :

what version of enblend is in this Hugin bundle? Issue the command `enblend --version` from the command line to know.
can you try to reproduce with a recent version of Hugin, that will likely have a more recent version of enblend included?

tags: added: enblend osx
Yuv (yuv) on 2010-12-02
Changed in hugin:
status: New → Triaged
rew (r-e-wolff) wrote :

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....

affects: hugin → enblend
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers