Description of problem: When I run exposition optimizer on a certain set of photos I get segfault Version-Release number of selected component (if applicable): hugin-2012.0.0-4.mga3 Steps to Reproduce: 1. load some photos 2. run exposition optimizer 3. wait for crash back-trace from gdb: (gdb) bt #0 0x00007fffe50eb9be in UNLOOP () from /usr/lib64/atlas/libatlas.so.3 #1 0x00007fffe50eb898 in ATL_daxpy () from /usr/lib64/atlas/libatlas.so.3 #2 0x00007fffe50eb263 in ATL_daxpby () from /usr/lib64/atlas/libatlas.so.3 #3 0x00007fffe517d7bd in ATL_dmm_axpy () from /usr/lib64/atlas/libatlas.so.3 #4 0x00007fffe517dd69 in ATL_dmmJKI () from /usr/lib64/atlas/libatlas.so.3 #5 0x00007fffe50ed2ea in ATL_dgemm () from /usr/lib64/atlas/libatlas.so.3 #6 0x00007fffea3be015 in cblas_dgemm () from /usr/lib64/atlas/libcblas.so.3 #7 0x00007ffff1e1e5a8 in ATL_dgetrfC () from /usr/lib64/atlas/liblapack.so.3 #8 0x00007ffff1e1e4b1 in ATL_dgetrfC () from /usr/lib64/atlas/liblapack.so.3 #9 0x00007ffff1e1e4b1 in ATL_dgetrfC () from /usr/lib64/atlas/liblapack.so.3 #10 0x00007ffff1e1e4b1 in ATL_dgetrfC () from /usr/lib64/atlas/liblapack.so.3 #11 0x00007ffff1e1e4b1 in ATL_dgetrfC () from /usr/lib64/atlas/liblapack.so.3 #12 0x00007ffff1e1e419 in ATL_dgetrf () from /usr/lib64/atlas/liblapack.so.3 #13 0x00007ffff1e224fb in atl_f77wrap_dgetrf_ () from /usr/lib64/atlas/liblapack.so.3 #14 0x00007ffff208878f in dgetrf_ () from /usr/lib64/atlas/liblapack.so.3 #15 0x00007ffff7ac3c4b in dAx_eq_b_LU () from /usr/lib64/hugin/libhuginbase.so.0.0 #16 0x00007ffff7ac1ef0 in dlevmar_dif () from /usr/lib64/hugin/libhuginbase.so.0.0 #17 0x00007ffff7508127 in HuginBase::PhotometricOptimizer::optimizePhotometric(HuginBase::PanoramaData&, std::vector<std::set<std::string, std::less<std::string>, std::allocator<std::string> >, std::allocator<std::set<std::string, std::less<std::string>, std::allocator<std::string> > > > const&, std::vector<vigra_ext::PointPairT<vigra::RGBValue<float, 0u, 1u, 2u> >, std::allocator<vigra_ext::PointPairT<vigra::RGBValue<float, 0u, 1u, 2u> > > > const&, AppBase::ProgressReporter&, double&) () from /usr/lib64/hugin/libhuginbase.so.0.0 #18 0x00007ffff75085e4 in HuginBase::SmartPhotometricOptimizer::smartOptimizePhotometric(HuginBase::PanoramaData&, HuginBase::SmartPhotometricOptimizer::PhotometricOptimizeMode, std::vector<vigra_ext::PointPairT<vigra::RGBValue<float, 0u, 1u, 2u> >, std::allocator<vigra_ext::PointPairT<vigra::RGBValue<float, 0u, 1u, 2u> > > > const&, AppBase::ProgressReporter&, double&) () from /usr/lib64/hugin/libhuginbase.so.0.0 #19 0x000000000058781c in OptimizePhotometricPanel::runOptimizer(std::set<unsigned int, std::less<unsigned int>, std::allocator<unsigned int> > const&) () #20 0x0000000000588898 in OptimizePhotometricPanel::OnOptimizeButton(wxCommandEvent&) () ... Reproducible: Steps to Reproduce:
Keywords: (none) => TriagedCC: (none) => fundawangVersion: Cauldron => 3Source RPM: (none) => hugin
Does this happens when you run this optimizer on all photos or just this certain set? Are they particularly large? Is there lots of free memory available--could it be hitting an OOM situation and handling it poorly? What is the specific crash that happens here?
CC: (none) => dan
It all looks to be related to problems I described here: https://bugs.mageia.org/show_bug.cgi?id=9569 It also doesn't look as problem with memory, but photos were quite big (4320x3240) and where 30-60 of them. The same conditions (gnome/kde4/xfce4) are valid here
Bug #9569 has a backtrace that goes through gtk + Oxygen, whereas this one looks like a pure calculation routine consisting of hugin and atlas. If you are confident that memory isn't an issue (which may be tough to prove since a temporary spike in memory usage wouldn't be seen by a statistical analyzer), then it's probably a hugin (or libatlas) problem that would be better reported upstream. Have you tried running hugin under valgrind and/or install the debug version of lib64atlas3-x86_64? That might show a bit more detail about the problem.
Mageia 3 changed to end-of-life (EOL) status 4 months ago. http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- The Mageia Bugsquad
Status: NEW => RESOLVEDResolution: (none) => OLD