enblend out of memory St9bad_alloc

[Milan Knizek]

Hello List!

I am not able to enblend higher resolution images with enblend-2.5 nor enblend-3.0 on FreeBSD-6.2 STABLE (gcc version 3.4.6 [FreeBSD] 20060305)

I have also recompiled enblend with "-g" option, but gdb does not find any debugging symbols anyway.

When I resize the input images to, say, 25%, enblend blends them without problem.

Any ideas?

Best regards,

Milan

Here is the output of enblend:

bash-2.05b$ enblend -v -o pano.tif pano_vsen0000.tif pano_vsen0001.tif

Input image "pano_vsen0000.tif" RGB ICC UINT16 position=0x0 size=9148x2676

Input image "pano_vsen0001.tif" RGB ICC UINT16 position=0x0 size=9148x2676

Output image size: [(0, 0) to (9148, 2676) = (9148x2676)]

Loading next image: pano_vsen0000.tif

assembled images bounding box: [(17, 740) to (2909, 2676) = (2892x1936)]

Loading next image: pano_vsen0001.tif

assembled images bounding box: [(1066, 744) to (3960, 2676) = (2894x1932)]

image union bounding box: [(17, 740) to (3960, 2676) = (3943x1936)]

image intersection bounding box: [(1066, 744) to (2909, 2676) = (1843x1932)]

Estimated space required for mask generation: 115MB

Creating blend mask: 1/4 2/4 3/4 4/4

Optimizing 1 distinct seam.

Strategy 1, s0: 1/4 2/4 3/4 4/4

Strategy 2: s0

Mask transition line bounding box: [(1816, 740) to (2282, 2676) = (466x1936)]

Using 8 blending levels

Region of Interest bounding box: [(1308, 740) to (2790, 2676) = (1482x1936)]

Estimated space required for this blend step: 277MB

Generating Gaussian pyramid: g0 g1 g2 g3 g4 g5 g6 g7

enblend: out of memory

St9bad_alloc

--

Milan Knížek

http://milan-knizek.net/

e-mail knizek {na} volny {v} cz

[Milan Knizek]

On Sunday 18 March 2007 22:01, Milan Knizek wrote:
> On Sunday 18 March 2007 20:46, Rob Park wrote:

> > On 3/18/07, Milan Knizek <kni...@volny.cz> wrote:
> > > When I resize the input images to, say, 25%, enblend blends them
> > > without problem.
> >

> > You need to use the -m option to tell enblend not to use more memory
> > than you have. I find setting -m to half of the physical RAM has good
> > results.
>
> On FreeBSD 6.2 I found that -m 512 fails, while -m 400 works (swap was not
> used at all).

For those having similar problem like me: FreeBSD has some hard limits for
processes. It is possible to tune the kernel a bit in /boot/loader.conf. I
have added:

# Kernel tunables - Memory limits
hw.physmem="3G"
kern.maxdsiz="2147483648" # 2GB
kern.dfldsiz="2147483648" # 2GB
kern.maxssiz="134217728" # 128MB

To see what the current limits are, run "ulimit -a"

Best regards,