hugin-devs team mailing list archive

[kaefert <kaefert@xxxxxxxxx>]

I'm affected by this bug too (at least that what it seems to me)
I'm using Ubuntu 13.04 and all packages are out of the default repositories.
I have 10GB ram and 20GB swap-space, but somehow the swap didn't get filled more than 10% when this error happened (which seems kind of strange to me)
Before I used LinuxMint14 (~Ubuntu 12.10) with 10GB of RAM and 10GB of swap and enblend made it much farer, and only crashed with this error around picture nr. 280 (there are 330 in total)

This is my output in the hugin logfile:

...
enblend: info: loading next image: name0226.tif 1/1
enblend: info: loading next image: name0227.tif 1/1

enblend: out of memory
enblend: std::bad_alloc
enblend: info: remove invalid output image "name.tif"
make: *** [name.tif] Error 1

So as I understand the workaround for this bug is to compile enblend
yourself and set some option "imagecache" to false or something? Could
someone guide me how to do this?

-- 
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/685105

Title:
  enblend fails to blend large pano

Status in Enblend:
  Confirmed

Bug description:
  Enblend failed with:

  enblend --compression=LZW -m 1200 -w -f135659x3947+0+1091 -o pano8110_l.tif ....
  ...
  enblend: info: loading next image: pano8110_l0000.tif 1/1
  enblend: out of memory
  enblend: std::bad_alloc

  This is a simple 0.5Gpixel panorama I shot. And agreed, Hugin did warn
  me that it might take a lot of memory.

  The thing is: There is no other tool to stitch this with, so I'll have to make do with hugin and its toolset....
  I thought there was an "imagecache" that would swap parts of images to disk...

To manage notifications about this bug go to:
https://bugs.launchpad.net/enblend/+bug/685105/+subscriptions