Hugin

Caught bad allocation processing HDR image

Bug #1423489 reported by Ben Owen
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Hugin
New
Undecided
Unassigned

Bug Description

> nona.exe -r hdr -m EXR -o "output.exr" -i 0 "process.txt"
caught exception: bad allocation

process.txt
=========

p f0 w4096 h4096 v90 k0 E0 R0 n"EXR"
m g1 i0 f0 m2 p0.00784314
i w14200 h7100 f4 v360 Ra0 Rb0 Rc0 Rd0 Re0 Eev0 Er1 Eb1 r0 p0 y0 TrX0 TrY0 TrZ0 j0 a0 b0 c0 d0 e0 g0 t0 Va1 Vb0 Vc0 Vd0 Vx0 Vy0 Vm5 Rt1 n"source.hdr"

source.hdr
========
Dimensions: 14200x7100
Bit depth: 96
Resolution: 72 dpi
Size: 264MB

System
======
Hugin 2014.0 32-bit ("nona version 2014.0.0.5da69bc383dd built by Matthew Petroff")
Windows 8.1 Pro (x64)
Core i7
8GB RAM

Works correctly when using 64-bit nona, or older build "0.7.0.3465 built by Guido".

Tags: nona windows x86
Ben Owen (b-l-owen)
tags: added: windows x86
Revision history for this message
tmodes (tmodes) wrote :

The problem is probably the size of your input image: 14200x7100 with bit depth 96. The 32 bit version of Hugin can only use 2 GB of RAM, even if you have more RAM installed. And the input file seems to be too big to be handled by nona 32-bit.

I see currently no easy way to workaround this problem in the 32 bit version. But you wrote already that the 64 bit version works fine, so it seems of low priority.

Revision history for this message
Ben Owen (b-l-owen) wrote :

As documented above:

> Works correctly when using 64-bit nona, or older [32-bit] build "0.7.0.3465 built by Guido".

Apologies if it was not clear that the older version was 32-bit.

As it works in an older 32-bit version of Nona, I believe that this is a regression - unless Nona has been rewritten and this was a known and accepted issue at the time?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.