nona: bad allocation error

Bug #678971 reported by nobody
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Hugin
Fix Released
Undecided
Unassigned

Bug Description

After about 18 hours working on this panorama, hugin failed with "error during stitching".
The computer is a quad 2.5GHz processor PC wiith 8GB RAM, running Vista 64.

Gordon
<email address hidden>

As requested, here is the complete log from the hug5F86 window:

C:\Program\ Files\ \(x86\)\Hugin\bin\nona -z PACKBITS -r ldr -m TIFF_m -o BaldyKnob-360 -i 0 C:\Users\Gordon\AppData\Local\Temp\hugB0E0.tmp
C:\Program\ Files\ \(x86\)\Hugin\bin\nona -z PACKBITS -r ldr -m TIFF_m -o BaldyKnob-360 -i 1 C:\Users\Gordon\AppData\Local\Temp\hugB0E0.tmp
C:\Program\ Files\ \(x86\)\Hugin\bin\nona -z PACKBITS -r ldr -m TIFF_m -o BaldyKnob-360 -i 2 C:\Users\Gordon\AppData\Local\Temp\hugB0E0.tmp
C:\Program\ Files\ \(x86\)\Hugin\bin\nona -z PACKBITS -r ldr -m TIFF_m -o BaldyKnob-360 -i 3 C:\Users\Gordon\AppData\Local\Temp\hugB0E0.tmp
C:\Program\ Files\ \(x86\)\Hugin\bin\nona -z PACKBITS -r ldr -m TIFF_m -o BaldyKnob-360 -i 4 C:\Users\Gordon\AppData\Local\Temp\hugB0E0.tmp
C:\Program\ Files\ \(x86\)\Hugin\bin\nona -z PACKBITS -r ldr -m TIFF_m -o BaldyKnob-360 -i 5 C:\Users\Gordon\AppData\Local\Temp\hugB0E0.tmp
C:\Program\ Files\ \(x86\)\Hugin\bin\nona -z PACKBITS -r ldr -m TIFF_m -o BaldyKnob-360 -i 6 C:\Users\Gordon\AppData\Local\Temp\hugB0E0.tmp
C:\Program\ Files\ \(x86\)\Hugin\bin\nona -z PACKBITS -r ldr -m TIFF_m -o BaldyKnob-360 -i 7 C:\Users\Gordon\AppData\Local\Temp\hugB0E0.tmp
C:\Program\ Files\ \(x86\)\Hugin\bin\nona -z PACKBITS -r ldr -m TIFF_m -o BaldyKnob-360 -i 8 C:\Users\Gordon\AppData\Local\Temp\hugB0E0.tmp
C:\Program\ Files\ \(x86\)\Hugin\bin\nona -z PACKBITS -r ldr -m TIFF_m -o BaldyKnob-360 -i 9 C:\Users\Gordon\AppData\Local\Temp\hugB0E0.tmp
C:\Program\ Files\ \(x86\)\Hugin\bin\nona -z PACKBITS -r ldr -m TIFF_m -o BaldyKnob-360 -i 10 C:\Users\Gordon\AppData\Local\Temp\hugB0E0.tmp
C:\Program\ Files\ \(x86\)\Hugin\bin\nona -z PACKBITS -r ldr -m TIFF_m -o BaldyKnob-360 -i 11 C:\Users\Gordon\AppData\Local\Temp\hugB0E0.tmp
C:\Program\ Files\ \(x86\)\Hugin\bin\nona -z PACKBITS -r ldr -m TIFF_m -o BaldyKnob-360 -i 12 C:\Users\Gordon\AppData\Local\Temp\hugB0E0.tmp
C:\Program\ Files\ \(x86\)\Hugin\bin\nona -z PACKBITS -r ldr -m TIFF_m -o BaldyKnob-360 -i 13 C:\Users\Gordon\AppData\Local\Temp\hugB0E0.tmp
C:\Program\ Files\ \(x86\)\Hugin\bin\nona -z PACKBITS -r ldr -m TIFF_m -o BaldyKnob-360 -i 14 C:\Users\Gordon\AppData\Local\Temp\hugB0E0.tmp
C:\Program\ Files\ \(x86\)\Hugin\bin\nona -z PACKBITS -r ldr -m TIFF_m -o BaldyKnob-360 -i 15 C:\Users\Gordon\AppData\Local\Temp\hugB0E0.tmp
C:\Program\ Files\ \(x86\)\Hugin\bin\nona -z PACKBITS -r ldr -m TIFF_m -o BaldyKnob-360 -i 16 C:\Users\Gordon\AppData\Local\Temp\hugB0E0.tmp
C:\Program\ Files\ \(x86\)\Hugin\bin\nona -z PACKBITS -r ldr -m TIFF_m -o BaldyKnob-360 -i 17 C:\Users\Gordon\AppData\Local\Temp\hugB0E0.tmp
C:\Program\ Files\ \(x86\)\Hugin\bin\nona -z PACKBITS -r ldr -m TIFF_m -o BaldyKnob-360 -i 18 C:\Users\Gordon\AppData\Local\Temp\hugB0E0.tmp
C:\Program\ Files\ \(x86\)\Hugin\bin\nona -z PACKBITS -r ldr -m TIFF_m -o BaldyKnob-360 -i 19 C:\Users\Gordon\AppData\Local\Temp\hugB0E0.tmp
C:\Program\ Files\ \(x86\)\Hugin\bin\nona -z PACKBITS -r ldr -m TIFF_m -o BaldyKnob-360 -i 20 C:\Users\Gordon\AppData\Local\Temp\hugB0E0.tmp
C:\Program\ Files\ \(x86\)\Hugin\bin\nona -z PACKBITS -r ldr -m TIFF_m -o BaldyKnob-360 -i 21 C:\Users\Gordon\AppData\Local\Temp\hugB0E0.tmp...

[Truncated; see "Full description" attachment]

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

Logged In: YES
user_id=35360
Originator: NO

oops, reclassifying. This is nona crashing with a memory error, did you run out of disk space on your c: drive?

Revision history for this message
Bruno Postle (brunopostle) wrote :

setting to pending as no response

Revision history for this message
sf-robot (sf-robot-users) wrote :

This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).

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

Other bug subscribers

Remote bug watches

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