Hi Ian,

thanks for the report.Could you try the current version, 0.7.0  (or better the one which comes with digikam 0.9.3beta2 or even better current svn)
and see if the crash persists?
(I don't observe it with a self-compiled version under debian etch)
Installation instructions are at: http://www.digikam.org/?q=download/svn
in particular below "Install digiKam in your Home Directory".

Independent of this, the above backtrace is cannot be used
to track down the problem, because there are no debugging symbols
(message "(no debugging symbols found)") related to digikam.
For this you have to compile digikam and enable debugging,
see http://www.digikam.org/?q=contrib under the heading
"If you are experiencing crashes with digiKam".

Thanks a lot in advance for your help,

Ard

I confirm that the crash happens (or not - at random) when exiting current svn version of showfoto. Despite compiling digiKam with --enable-debug=full, the KDE crash handler showed only:

8<---------------------------------
This backtrace appears to be of no use.
This is probably because your packages are built in a way which prevents creation of proper backtraces, or the stack frame was seriously corrupted in the crash.

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
8<---------------------------------

I tried running it under a debugger and it appears to crash after the main function returns (so all local objects are already deleted), during some Qt library cleanup. Here's the stack trace from the debugger:

8<---------------------------------
malloc_consolidate () from /lib/libc.so.6
_int_free () from /lib/libc.so.6
free () from /lib/libc.so.6
operator delete () from /usr/lib/libstdc++.so.6
operator delete[] () from /usr/lib/libstdc++.so.6
QGDict::~QGDict () from /opt/qt/lib/libqt-mt.so.3
QMemberDict::~QMemberDict () from /opt/qt/lib/libqt-mt.so.3
QMetaObject::~QMetaObject () from /opt/qt/lib/libqt-mt.so.3
QMetaObjectCleanUp::~QMetaObjectCleanUp () from /opt/qt/lib/libqt-mt.so.3
?? () from /opt/qt/lib/libqt-mt.so.3
QTextEdit::MetaObj () from /opt/qt/lib/libqt-mt.so.3
?? () from /lib/libc.so.6
?? ()
__cxa_finalize () from /lib/libc.so.6
8<---------------------------------

Pawel,

Try to use valgrind to give a backtrace. Look in HACKING file, there is a section witch describe how to use it.

Gilles

I confirm the crash on 0.6.0 (debian lenny) BUT, strange as it seems, it only happens if I quit showfoto clicking the window title-bar button. If I use the file->quit menu item, showfoto never ever crashes on exit. This has been confirmed to me by one frequent user here.

Moreover, upon investigating this behavior, I noticed this crash does not show up with less than 2 files loaded in showfoto !

This is a constant (reproduced persistently tonight and advertised for many monthes by the aleady quoted user) behavior on 2 lenny boxes but it happears apparently more randomly on a (lenny too) laptop: after crashing once tonight (with an unusual ~3 seconds delay between the window closing and the sigsev dialog box) I couldn't manage to make it show up once again.

All 3 tests boxes are running regularly updated debian lenny and KDE.

Hope this helps.

*** Bug 152217 has been marked as a duplicate of this bug. ***

Ian,

Crash still exist when you update to last stable showfoto 0.7.0 ?

Thanks in advance

Gilles Caulier

Pawel, Ian, Phep,

Try to use valgrind against current showfoto implementation from svn like this :

valgrind --tool=memcheck --leak-check=full --error-limit=no showfoto

Do not report any fatal error about wrong memory management in showfoto. I cannot reproduce the crash here. I can see few problem in Qt or kdelibs but not from showfoto implementation.

Please just run showfoto under valgrind, open few images, and close it. Just report the console backtrace in this file for investiguations.

Thanks in advance

Gilles Caulier

Yesterday 0.9.3-2 pkgs were uploaded to Debian/Sid.  This pkgs fixed
another showfoto crash on exit in Kubuntu:
https://bugs.launchpad.net/ubuntu/+source/digikam/+bug/206354

So give the new pkgs a try.

Achim

Though I made all sorts of tries, 0.7.0 (debian lenny pkg 0.9.3-1+b1 or 0.9.3-2) does not seem to be subject to this bug anymore.

Thanks guys !

phep

Thanks. I close this file now.

Gilles Caulier

Sorry to disappoint but this is not the case.  Debian Lenny pkg 0.9.3-2 
still crashes (signal 11)

Regards,
Ian.



phep wrote:
[bugs.kde.org quoted mail]

Hi Ian, 

to proceed in some way, your help is needed:
A full backtrace for the crash is needed.
For this you have to compile digikam and enable debugging,
see http://www.digikam.org/?q=contrib under the heading
"If you are experiencing crashes with digiKam".
The other option is that you install the corresponding packages
which include debugging information.
(From where did you obtain the packages? E.g. use `aptitude show digikam`)

Arnd

Still have a crash problem on exit with version 0.6.0 in Ubuntu Gutsy 7.10
If I open Showfoto and close it without opening a picture I don't have a crash error.
But if I open and view even one picture I will get a crash error report. This will happen if I use the Quit button or click on the X in window to close it.

Below is the Backtrace. Package was downloaded from the Ubuntu repository.

TaZMAn


(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1236216128 (LWP 8246)]
[New Thread -1240372336 (LWP 8261)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#6  0xb65b20c0 in ?? () from /lib/tls/i686/cmov/libc.so.6
#7  0xb738c880 in ?? () from /usr/lib/libkdecore.so.4
#8  0x00000001 in ?? ()
#9  0xb7fb9ff4 in ?? () from /lib/ld-linux.so.2
#10 0xb7c05c38 in ?? ()
#11 0xbfbf3b7c in ?? ()
#12 0xb6672fd5 in ?? () from /lib/tls/i686/cmov/libc.so.6
#13 0xb7fa8166 in ?? () from /lib/ld-linux.so.2
#14 0xb65b3b6e in ?? () from /lib/tls/i686/cmov/libc.so.6
#15 0xb7c05a80 in ?? ()
#16 0xb739bdef in ?? () from /usr/lib/libkdecore.so.4
#17 0x479ae749 in ?? ()
#18 0xb65b36c1 in ?? () from /lib/tls/i686/cmov/libc.so.6
#19 0xb6691148 in ?? () from /lib/tls/i686/cmov/libc.so.6
#20 0x081ca548 in ?? ()
#21 0xb667613c in ?? () from /lib/tls/i686/cmov/libc.so.6
#22 0x0856db80 in ?? ()
#23 0xb7c05a80 in ?? ()
#24 0x00050478 in ?? ()
#25 0xb66761a0 in ?? () from /lib/tls/i686/cmov/libc.so.6
#26 0x08502780 in ?? ()
#27 0xb6691148 in ?? () from /lib/tls/i686/cmov/libc.so.6
#28 0xb668fff4 in ?? () from /lib/tls/i686/cmov/libc.so.6
#29 0xb667613c in ?? () from /lib/tls/i686/cmov/libc.so.6
#30 0x084cc1c8 in ?? ()
#31 0xbfbf3b9c in ?? ()
#32 0xb65b7800 in free () from /lib/tls/i686/cmov/libc.so.6
#33 0xb65b7800 in free () from /lib/tls/i686/cmov/libc.so.6
#34 0xb6770d81 in operator delete () from /usr/lib/libstdc++.so.6
#35 0xb6770ddd in operator delete[] () from /usr/lib/libstdc++.so.6
#36 0xb7439c89 in KZoneAllocator::~KZoneAllocator ()
   from /usr/lib/libkdecore.so.4
#37 0xb7439cf0 in ?? () from /usr/lib/libkdecore.so.4
#38 0xb7599a40 in ?? () from /usr/lib/libkdecore.so.4
#39 0xb668fff4 in ?? () from /lib/tls/i686/cmov/libc.so.6
#40 0xbfbf3c58 in ?? ()
#41 0xb65778c1 in __cxa_finalize () from /lib/tls/i686/cmov/libc.so.6
Backtrace stopped: frame did not save the PC

Same here. no debug info available...

Gilles Caulier

Hi TaZMAn,

could you try with the recent 0.7.0 version of showfoto?
Packages for gutsy can be found at
http://www.mpe.mpg.de/~ach/kubuntu/gutsy/

In case you still observe crashes, you also need to install the dbg
package, so that a crash report with debugging information
is generated.

Thanks a lot in advance, Best, Arnd

Hi Arnd,

I uninstalled showfoto then went to the link you posted.
Had to install 2 packages to fulfill the dependencies for the new showfoto package.
Then I installed showfoto 0.7.0

Tried it out and it no longer gives that error message.

It fixed the problem. Thank you so much!
And a big thanks to everyone involved with this project.
It's the best photo editor I have come across in any Linux distro.

Will heavily test out this version and will report any problems if any.

Thanks again!

TaZMAn

Nobody can run showfoto under valgrind as below :

valgrind --tool=memcheck --leak-check=full --error-limit=no showfoto

... and report the console backtrace in this file.

If something is wrong, i will see imediatly...

Note: on my computer all is fine. showfoto never crash, and backtrace only report internal problem from Qt, KDE or C++ library

Gilles Caulier

Hum, i can reproduce the crash now under Mandriva 2008.1, just when i quit application after to haev open a PNG file.

Backtrace is below :

/bin/sh -c libtool gdb /home/gilles/Documents/Devel/SVN/branches/graphics/digikam/showfoto/showfoto --interpreter=mi2 -quiet
Using host libthread_db library "/lib/i686/libthread_db.so.1".
(gdb) bt
bt
#0  0xb5f553a0 in QWidget::setUpdatesEnabled () from /lib/i686/libc.so.6
#1  0xbfec07e8 in ?? ()
#2  0xb7fbd7d4 in ?? ()
#3  0x00000014 in ?? ()
#4  0xb5f56df3 in QWidget::setUpdatesEnabled () from /lib/i686/libc.so.6
#5  0xb732d560 in ?? ()
#6  0xb70cd8bc in QWidget::setUpdatesEnabled () from /usr/lib/libkdecore.so.4
#7  0x03d66f09 in ?? ()
#8  0xb5f56941 in QWidget::setUpdatesEnabled () from /lib/i686/libc.so.6
#9  0xb602f128 in QWidget::setUpdatesEnabled () from /lib/i686/libc.so.6
#10 0xb602f120 in QWidget::setUpdatesEnabled () from /lib/i686/libc.so.6
#11 0xb6015df8 in QWidget::setUpdatesEnabled () from /lib/i686/libc.so.6
#12 0x085908b8 in ?? ()
#13 0xb602dff4 in ?? () from /lib/i686/libc.so.6
#14 0x000129a8 in ?? ()
#15 0xb6015e5c in QWidget::setUpdatesEnabled () from /lib/i686/libc.so.6
#16 0x0857a0d0 in ?? ()
#17 0xb602f128 in QWidget::setUpdatesEnabled () from /lib/i686/libc.so.6
#18 0xb602f120 in QWidget::setUpdatesEnabled () from /lib/i686/libc.so.6
#19 0xb6015df8 in QWidget::setUpdatesEnabled () from /lib/i686/libc.so.6
#20 0xbfec0808 in ?? ()
#21 0xb5f5aaf0 in free () from /lib/i686/libc.so.6
#22 0xb5f5aaf0 in free () from /lib/i686/libc.so.6
#23 0xb610cd91 in operator delete () from /usr/lib/libstdc++.so.6
#24 0xb610cded in operator delete[] () from /usr/lib/libstdc++.so.6
#25 0xb715aca5 in KZoneAllocator::~KZoneAllocator () from /usr/lib/libkdecore.so.4
#26 0xb715ad0d in QWidget::setUpdatesEnabled () from /usr/lib/libkdecore.so.4
#27 0xb5f1a9b8 in __cxa_finalize () from /lib/i686/libc.so.6
#28 0xb712f6a3 in QWidget::setUpdatesEnabled () from /usr/lib/libkdecore.so.4
#29 0xb73013a0 in ?? () from /usr/lib/libkdecore.so.4
#30 0xb72fd6a4 in QWidget::setUpdatesEnabled () from /usr/lib/libkdecore.so.4
#31 0xbfec08d8 in ?? ()
#32 0xb72a5c4c in _fini () from /usr/lib/libkdecore.so.4
Backtrace stopped: frame did not save the PC
^done

Marcel, Arnd, Mik, Gerhard,

Can you reproduce this crash under GDB with a better suitable backtrace ?

Gilles

no crash here ...

Arnd,

I can always reproduce the problem using loading this file :

http://digikam3rdparty.free.fr/TEST_IMAGES/METADATA/digiKam/photo-000048.png

Like this : showfoto ./photo-000048.png

The image is displayed imediatly on screen. I toogle to Fit on screen mode, and i quit showfoto using File/Quit (it's important)

I don't perform anything in showfoto (plugins, transformation, etc)

Thumbbar is displayed on the bottom. right sidebar is open with histogram view.

Gilles

Arnd,

With valgrind, showfoto do not crash, but it report this trace :

==31266== Invalid read of size 4
==31266==    at 0x5260CE0: QImage::~QImage() (in /usr/lib/qt3/lib/libqt-mt.so.3.3.8)
==31266==    by 0x5FC06C3: exit (in /lib/i686/libc-2.7.so)
==31266==    by 0x5FAA397: (below main) (in /lib/i686/libc-2.7.so)
==31266==  Address 0x8ef9f08 is 0 bytes inside a block of size 64 free'd
==31266==    at 0x402105C: operator delete(void*) (in /usr/lib/valgrind/x86-linux/vgpreload_memcheck.so)
==31266==    by 0x5260D08: QImage::~QImage() (in /usr/lib/qt3/lib/libqt-mt.so.3.3.8)
==31266==    by 0x5FC06C3: exit (in /lib/i686/libc-2.7.so)
==31266==    by 0x5FAA397: (below main) (in /lib/i686/libc-2.7.so)
==31266==
==31266== Invalid write of size 4
==31266==    at 0x5260CE7: QImage::~QImage() (in /usr/lib/qt3/lib/libqt-mt.so.3.3.8)
==31266==    by 0x5FC06C3: exit (in /lib/i686/libc-2.7.so)
==31266==    by 0x5FAA397: (below main) (in /lib/i686/libc-2.7.so)
==31266==  Address 0x8ef9f08 is 0 bytes inside a block of size 64 free'd
==31266==    at 0x402105C: operator delete(void*) (in /usr/lib/valgrind/x86-linux/vgpreload_memcheck.so)
==31266==    by 0x5260D08: QImage::~QImage() (in /usr/lib/qt3/lib/libqt-mt.so.3.3.8)
==31266==    by 0x5FC06C3: exit (in /lib/i686/libc-2.7.so)
==31266==    by 0x5FAA397: (below main) (in /lib/i686/libc-2.7.so)

Look like the gdb backtrace reported before ask than a delete operator crash showfoto. This valgrind report appears just after to quit. Sound like it's the problem...

...but my valgrind backtrace is not really suitable here. Can you make a better one, with the source code relevant where the delete operator is processed ?

Gilles

no crash for this image as well...

With my commit #808273, i have fixed the invalid memory manipulation witch is reported by valgrind in #21.

I suspect that it's the problem and crash showfoto sometime.

If somebody can checkout svn and try...

Gilles Caulier

For me the crash is not reproductible now.

I close this file as WORKSFORME

Gilles