hugin-devs team mailing list archive

[Yuv <679281@xxxxxxxxxxxxxxxxxx>]

Can you reproduce this?

If yes, do load the images and lens data but instead of clicking
"Optimize now!" or "Align" save the project and post the .pto file here.
Thanks

** Tags added: optimizer

** Changed in: hugin
       Status: New => Incomplete

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

Title:
  Crash during optimize (Mac Leopard)

Status in Hugin - Panorama Tools GUI:
  Incomplete

Bug description:
  After loading images and lens data, Hugin hangs and then crashes pretty much every time I click the "Optimize now!" button (or during the optimize step of the Assistant's "Align" step).  It's possible this bug is in one of the libraries used by Hugin, but I figure I should report it here first.

I have seen this behavior every time I attempt to use Hugin on my PPC G4 Mac laptop and at least some of the time when testing on an Intel iMac, both running Mac OS 10.5.8.  I first saw the error on my PPC while using Hugin 0.6.1 (it's been a while since I last used the program; I've upgraded from 10.3 to 10.5 since the last time I used it successfully), but I am getting similar crash logs with 0.8.0 on both PPC and Intel platforms (I've tried several different precompiled binary packages linked from the Hugin site).  I've observed it on the PPC in two or three entirely different panorama stitching projects (with two or three images each, one of which had worked when I first tried it a year or two ago) and on the Intel during one attempt to do perspective correction on a single image (a later attempt worked for that one; I don't know what could have changed).

I'm attaching a crash reporter log from my Intel iMac, which shows the characteristic signature that I've seen on both machines: a crash in Thread 0, with a variety of addresses at the top of the stack (in this case, 0x160243c8, but sometimes just 0 or 0xc0000000).  The key points of commonality are the top few stack lines:

0   ???                                 0x160243c8 0 + 369247176
1   libSystem.B.dylib                   0x96733cb4 setlocale + 945
2   libpano13.dylib                     0x003b5e6c ParseScript + 44
3   net.sourceforge.hugin.base_wx       0x0157aad2 HuginBase::PTools::optimize(HuginBase::PanoramaData&, char const*) + 82
...

The "setlocale" function called by "ParseScript" called by "optimize" is always the same.  For what it's worth, I've sometimes also run Hugin from the terminal on my PPC, and very early in the optimizing process I see a message like:

"Hugin(750,0xa0ab6820) malloc: *** error for object 0x2237a00: double free
*** set a breakpoint in malloc_error_break to debug"

which appears even before all the "Optimizing variables:" steps are printed.  But after optimization gets the distance down to a respectable size, program execution just ends with a seg fault or bus error (and Apple's crash reporter dialog box, eventually).

This is frustrating, because it makes Hugin entirely unusable on my PPC laptop and (I expect) frustrating to use much on my Intel iMac.  I hope you can track it down!