Crash switching to optimize tab

Bug #1895623 reported by Bob Babcock
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Hugin
New
Undecided
Unassigned

Bug Description

I'm stitching pairs of B&W JPGs, scanned from old 4x5 negatives too big for my Canon 9000F.
Windows 10 1909, 64 bit
Hugin Version: 2019.2.0.b690aa0334b5 built by Thomas

I sometimes get a crash when switching to the optimize tab.
I don't think I've had it crash on the first pair of images, only later ones.
This is before the .pto file is created. Repeating with the same images always works.
Dump file is attached.

The process I'm using:
If not first run, hit ctrl-N for new project.
Drop 2 images on Hugin, enter 10 for each HFOV.
Set optimize/geometric to Custom parameters.
Create control points with default Hugin's CPFind (typically get 20 or so).
Switch to optimizer tab. (Control point finder works so well I don't bother to check it.)
** This is where Hugin may crash, before doing anything on the tab.
Otherwise, I check Yaw, X(TrX), Y(TrY), Z(TrX) for 2nd image and optimize.
On stitcher tab, calculate optimal size and fit crop to images.
Stitch!

Does a great job; join is not visible.

Info from System tab of Help:
Operating System: Windows 10 (build 18363), 64-bit edition
Architecture: 64 bit
Free memory: 11495696 kiB
Active Codepage: 1252 (Western European Windows)

Hugin
Version: 2019.2.0.b690aa0334b5 built by Thomas
Path to resources: C:\App\Hugin\share\hugin\xrc\
Path to data: C:\App\Hugin\share\hugin\data\
Hugins camera and lens database: C:\Users\bob\AppData\Roaming\hugin\camlens.db
Multi-threading using C++11 std::thread and OpenMP
Monitor profile: C:\WINDOWS\system32\spool\drivers\color\sRGB Color Space Profile.icm

Libraries
wxWidgets: wxWidgets 3.1.4
wxWidgets Library (wxMSW port)
Version 3.1.4 (Unicode: wchar_t, debug level: 1),
compiled at Oct 31 2019 08:12:14

Runtime version of toolkit used is 10.0.

libpano13: 2.9.20
Exiv2: 0.27.2
SQLite3: 3.30.1
Vigra: 1.11.1
LittleCMS2: 2.9

Revision history for this message
Bob Babcock (wssddc) wrote :
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.