nona: bad allocation with high-resolution panorama

Bug #678946 reported by nobody
28
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Hugin
Confirmed
Medium
Unassigned

Bug Description

Received error message:

"D:\hugintest\hugin_0.7.0.3113\bin\nona -z PACKBITS -r ldr -m TIFF_m -o sp -i 0 C:\Users\ADHUIK~1\AppData\Local\Temp\hug70AA.tmp
caught exception: bad allocation
make: *** [sp0000.tif] Error 1"

And a request to report. I tried to run speedtest.pts which outputs 80713*15850 pixel image based on 337 input images, see http://hdview.at/speedtest/index.html.

Probably because I only have 2GB of RAM ...

My Quad Core 2,4 GHz took over seven hours to create a 40000*7855 imagefile from the same speedtest.pts. This is rather slow compared to other software, see resultspage of test: http://hdview.at/speedtest/results.html

Now is time for compliments: I like Hugin, I'm using it for at least two years. I'm really impressed by the development of new features in the last year (enfuse!) and just want to say: keep up the good work.

Ad Huikeshoven
The Hague
(aka Dedalus)

Revision history for this message
nobody (nobody-users) wrote :

I also encountered this error on a quad-core, and I have 4GB of RAM. I suspected memory might be an issue, but when I watched the performance monitor the usage never went above 1.8GB, so it doesn't seem that simple.

Revision history for this message
rew (r-e-wolff) wrote :

His Email is firstname dot lastname at gmail dot com

tags: added: malloc nona windows
Changed in hugin:
status: New → Incomplete
Revision history for this message
rew (r-e-wolff) wrote :

Email sent. asked to confirm on latest version (2010.4 beta).

Revision history for this message
Yuv (yuv) wrote :
Changed in hugin:
status: Incomplete → Confirmed
Revision history for this message
rew (r-e-wolff) wrote :

Ad's pano is 0.8 Gigapixels and crashes with a bad alloc on "nona", while mine is 0.5 Gpixels, and crashes at the "enblend" step Bug #685105 . (he's on windows, I use Linux).

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

Duplicates of this bug

Other bug subscribers

Remote bug watches

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