Summary: | digikam crash at startup | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | Peter Möller <gorgonz> |
Component: | DImg-Plugins | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | caulier.gilles, marcel.wiesweg |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 1.0.0 | |
Sentry Crash Report: | |||
Attachments: |
backtrace exception
console messages as text logging the console output from cmake with errors building kexiv2 |
Description
Peter Möller
2009-06-20 13:08:08 UTC
additional: this happens even if there is no camera attached via usb. will not do it myself, but this bug should get a higher prio, because i must uninstall digikam in order to have a change to see the contents of the camera again SVN commit 984269 by mwiesweg: Catch std::bad_alloc around the main image data allocation - with very big images or corrupt headers, width or height information may be fatally large. CCBUG: 197254 M +24 -4 tiffloader.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=984269 Peter please test with the fix. This crash is related to loading a (very large) TIFF file. Hi Marcel, hab ein wenig gebraucht, bis ich klar war, was da zu tun ist. Habe jetzt exiv2 und LibRaw libs gebaut und konnte dadurch den gefixten Stand von digikam mit "cmake ." compilieren. allerdings find ich jetzt nix zum Ausführen. Das original digikam ist wohl noch normal installiert, also wurde kein neuerer Stand darüber installiert. Vielleicht fehlt ja noch der richtige Befehl zum Installieren. Kannst Du mir da einen Tipp geben? Gruß Peter Möller Marcel Wiesweg schrieb: > https://bugs.kde.org/show_bug.cgi?id=197254 > > > Marcel Wiesweg <marcel.wiesweg@gmx.de> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |marcel.wiesweg@gmx.de > > > > > --- Comment #4 from Marcel Wiesweg <marcel wiesweg gmx de> 2009-06-20 16:41:09 --- > Peter please test with the fix. > This crash is related to loading a (very large) TIFF file. > > sorry for the wrong language. Calling make with the fixed code brings 2 errors. Is there a hint, what i should do? [ 42%] Building CXX object digikam/CMakeFiles/digikam.dir/dbstatdlg.o /extra/install/11.1/packages/kde4-graphics/digikam/digikam/dbstatdlg.cpp: In constructor ‘Digikam::DBStatDlg::DBStatDlg(QWidget*)’: /extra/install/11.1/packages/kde4-graphics/digikam/digikam/dbstatdlg.cpp:85: error: ‘class QList<Digikam::AlbumInfo>’ has no member named ‘length’ /extra/install/11.1/packages/kde4-graphics/digikam/digikam/dbstatdlg.cpp:90: error: ‘class QList<Digikam::TagInfo>’ has no member named ‘length’ make[2]: *** [digikam/CMakeFiles/digikam.dir/dbstatdlg.o] Fehler 1 make[1]: *** [digikam/CMakeFiles/digikam.dir/all] Fehler 2 @#5: There is a self-compiling recipe somewhere on digikam.org as well. But you already succeeded ;-) Normally, type "make" to compile and "make install", as root, to install. (Check that the existing binary is really replaced and the new one is not installed in /usr/local but I think that should work.) @#6: This was a Qt-4.5 only commit and should be fixed in current SVN Created attachment 34850 [details]
backtrace exception
Created attachment 34851 [details]
console messages as text
meanwhile i was able to build rev 987807, which is beta2 family. The behaviour changed in so far that i see the list of picture previews until to a certain one. About 10 sec later digikam still crashes, but i'm able to identify the bad pictures now. They were created by me using hugin to combine pictures. Of course there might be handling errors, because it was the first usage of the program. In fact other programs like gimp also fail to open it, but gimp wan't crash. Still it could be a lucky situation, that i did some mistakes, because digikam might avoid to crash in the future there ;-) Since the pictures are pretty big, i don't know how to offer them (1GB, resp. 2GB of size). And i don't have the webspace to upload them. So here some additional infos instead. Exception backtrace and the console messages as file attachment. First: you will not be able to open such huge images with digikam unless you have huge amounts of memory. Simple reason: digikam's image editor does not use tiling but one big chunk of memory. This is absolutely sufficient for photos. But a file of 2GB compressed will need memory of >2GB as a chunk. No wonder it fails. Now to your backtraces. The XIO error indicates that anything before went wrong and you dont get to the point where it went wrong unfortunately. Sometimes is helps to start digikam directly under gdb and to provoke the crash. Or running digikam under valgrind may provide valuable information. Unfortunately I dont have huge images to test right now. I may try to combine a few hundred images with hugin one day ;-) of course i like non crashing applications best ;-). Lets see what we have: - the originating bug is fixed. - there is still a crash at a later time I give it into your hand, how the story is continued. Its ok to close this one, but it might be a good idea to catch the other situation with too big pictures in a similar way. But maybe this is ok already, because the hugin-created pictures are unusable and therefore corrupted anyway. SVN commit 990986 by mwiesweg: Check that the newly created QImage is not null, which may happen if memory allocation fails. CCBUG: 197254 M +6 -0 dimg.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=990986 At a second glance your backtrace was indeed quite useful. Please try again...there should also be an error message on the console (enable 50003 with kdebugdialog) Thanks tried to verify it, but could nor build successfully. Here my steps: -------------------------------------------------------------------------------- this is script 1 to get updates: ok, have SVN release 991184 now -------------------------------------------------------------------------------- cd /extra/install/11.1/packages svn co -N svn://anonsvn.kde.org/home/kde/branches/KDE/4.2/kdegraphics cd kdegraphics svn up libs svn up cmake # To Checkout the latest digiKam and Kipi-plugins SVN source for KDE4: cd .. svn co -N svn://anonsvn.kde.org/home/kde/trunk/extragear/graphics cd graphics svn up digikam svn up kipi-plugins svn up cmake -------------------------------------------------------------------------------- Next step configure: -------------------------------------------------------------------------------- cd /extra/install/11.1/packages/kdegraphics cmake . -------------------------------------------------------------------------------- Targets kipi, kdcraw, kdc_emu, identify, mem_image, raw2png, simple_dcraw including those *_automoc are ok. Problem with kexiv2. Look at the Log cmake.log among the attachments Did not see this before. Did i get into an unlucky moment, where sources are not consistent or did i do something wrong? Created attachment 35037 [details]
logging the console output from cmake with errors building kexiv2
Strange. Some old object files around? Try "make clean" or remove build directory, and try again. Hi Marcel, here are the good news: Yesterday i changed to kde 4.3 and found beta3 in the playground. So this is a pretty good 'work around my building problems' ;-) Result: Full success! Digikam works as expected now Feel free to close it now. |