abrt version: 1.1.13 architecture: x86_64 Attached file: backtrace cmdline: /usr/bin/hugin comment: Tried to create a panorama, obviously chose an invalid value for HFOV (either 1 or 0 - can't remember) and got a dialog from hugin about an invalid value and when pressed ok/yes got the abrt crash popup. component: hugin executable: /usr/bin/hugin kernel: 2.6.35.6-48.fc14.x86_64 package: hugin-2010.2.0-1.fc14 reason: Process /usr/bin/hugin was killed by signal 11 (SIGSEGV) release: Fedora release 14 (Laughlin) time: 1289085214 uid: 1000 How to reproduce ----- 1.opened hugin 2.attempted to create a panorama 3.obviously chose some incorrect value for HFOV (either 1 or 0 - can't remember) 4.got the abrt crash popup
Created attachment 458501 [details] File: backtrace
I can't reproduce, can you remember where you entered the invalid HFOF, was it for the input photos or the output panorama?
Created attachment 459623 [details] tar.gz of the files I was trying to create a panorama with I had never used hugin before, so I decided to try it on a couple of files that would guarantee some recognizable results, so I used the a scan of an odd shaped game box that I had made. As to where I put in the invalid results, and even what they were, I cannot remember. Most likely this crash was caused by "operator error", meaning I did put in an invalid input and most likely overrode the "are you sure you sure you want to shoot yourself in the foot?" prompts.... Sorry I haven't been more help...
Package: hugin-2010.2.0-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Creating a stereographic panorama of about 10 x 12 megapixel images 2. Auto sizing tool reckoned a final export resolution of 10 gigapixels(!) 3. When stitching a panorama of this size, it crashed after about a minute of consuming all system RAM and CPU
(In reply to comment #4) > Package: hugin-2010.2.0-1.fc14 > > How to reproduce > ----- > 1. Creating a stereographic panorama of about 10 x 12 megapixel images > 2. Auto sizing tool reckoned a final export resolution of 10 gigapixels(!) > 3. When stitching a panorama of this size, it crashed after about a minute of > consuming all system RAM and CPU Hi Jonathan, you discovered that stereographic is a weird projection. Unfortunately Hugin is doing the right thing, a very wide stereographic image has to be that size to avoid downsampling in the middle. The development version of Hugin now has a warning pop-up whenever it is about to create such a large image. The usual recommendation is to always stitch a spherical panorama to equirectangular projection, you can then load this into a new Hugin project and produce whatever stereographic (or other) views you like.
Hi Bruno, Thanks for this. I didn't think there was a problem with the auto sizing tool choosing 10 gigapixels - it seems reasonable. I reported this bug just in case it was possible/desirable to include some error trapping either to warn the user they are about to perform a large operation, or to prevent Hugin from trying to use more than the available RAM (etc). Thanks, Jonathan
*** Bug 684449 has been marked as a duplicate of this bug. ***
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping