hugin-devs team mailing list archive

[rew <679917@xxxxxxxxxxxxxxxxxx>]

Dear Thomas,

I was working on a project. Instead of putting my images around the circle hugin placed all images at 0,0,0. That is not how I shot things. So I went to the "preview" window, and tried dragging the images, so that they wouldn't be on top of eachother. That's when HUGIN ITSELF CRASHED. 
IT TOOK ALL MANUAL CONTROLPOINT EDITS WITH IT. NO SAVING POSSIBLE. PROCESS GONE.  DATA GONE. 

Your assumption that it happened when stitching or that no dataloss
happened is WRONG.

This IS  a real data-loss problem. I'm FINE with the developers not
getting around it before christmas. But PLEASE do not put this as
"wishlist" again. It is a significant problem.

This, saving the intermediate hugin file every now and then, is a
surefire way of diminishing the consequences of an unexpected crash. If
we take this seriously, a day of grudgework will reduce the severity of
an unexpected crash to "bad luck, just restore from the autosave".
Otherwise all crashes HAVE to be considered a showstopper.

** Changed in: hugin
   Importance: Wishlist => High

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

Status in Hugin - Panorama Tools GUI: Confirmed

Bug description:
Hugin just crashed on me. Pre 0.7.0 this happened so often that I knew I had to save often, or risk losing my work. 

So far this is the first since I went to 0.7.0. Now 0.8.0 crashed on me.... However I'm most pissed that a pto file got saved to run "nona", but this gets (I think) cleaned up after running nona. So now I'm left with a project file with hours of work missing. 

PLEASE write a backup pto file where I can find it, or mention "this project had unsaved changes when hugin crashed, load the backup file?" when I start it. (then I don't need to know where the backup is stored...).