Bug 139358 - Crash when closing DigiKam [backtrace]
Summary: Crash when closing DigiKam [backtrace]
Status: RESOLVED WORKSFORME
Alias: None
Product: digikam
Classification: Applications
Component: Portability-Runtime (show other bugs)
Version: 0.9.0
Platform: Gentoo Packages Linux
: NOR crash
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-12-29 16:09 UTC by Dik Takken
Modified: 2022-01-23 11:40 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In: 7.6.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dik Takken 2006-12-29 16:09:21 UTC
Version:           0.9.0-rc2 (using KDE KDE 3.5.5)
Installed from:    Gentoo Packages
OS:                Linux

When I just closed DigiKam, it crashed. This happened just once.

Backtrace:

Using host libthread_db library "/lib/libthread_db.so.1".
`system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols.
[Thread debugging using libthread_db enabled]
[New Thread -1238878544 (LWP 9928)]
[KCrash handler]
#6  0xb6b1131a in QTextString::clear () from /usr/qt/3/lib/libqt-mt.so.3
#7  0xb6b113bd in QTextString::~QTextString ()
   from /usr/qt/3/lib/libqt-mt.so.3
#8  0xb6af9c46 in QTextParagraph::~QTextParagraph ()
   from /usr/qt/3/lib/libqt-mt.so.3
#9  0xb6b1c0c4 in QTextDocument::clear () from /usr/qt/3/lib/libqt-mt.so.3
#10 0xb6b274d9 in QTextDocument::~QTextDocument ()
   from /usr/qt/3/lib/libqt-mt.so.3
#11 0xb6b3261d in QSimpleRichText::~QSimpleRichText ()
   from /usr/qt/3/lib/libqt-mt.so.3
#12 0xb6b6ae89 in QLabel::clearContents () from /usr/qt/3/lib/libqt-mt.so.3
#13 0xb6b6d051 in QLabel::~QLabel () from /usr/qt/3/lib/libqt-mt.so.3
#14 0xb6ae79ab in QWidget::~QWidget () from /usr/qt/3/lib/libqt-mt.so.3
#15 0xb6debcb5 in QFrame::~QFrame () from /usr/qt/3/lib/libqt-mt.so.3
#16 0xb6ae79ab in QWidget::~QWidget () from /usr/qt/3/lib/libqt-mt.so.3
#17 0xb7dd3840 in ~ImagePropertiesTab (this=0x84c1cf0)
    at imagepropertiestab.cpp:319
#18 0xb6ae79ab in QWidget::~QWidget () from /usr/qt/3/lib/libqt-mt.so.3
#19 0xb6beaa76 in QWidgetStack::~QWidgetStack ()
   from /usr/qt/3/lib/libqt-mt.so.3
#20 0xb6ae79ab in QWidget::~QWidget () from /usr/qt/3/lib/libqt-mt.so.3
#21 0xb6bcdcf8 in QSplitter::~QSplitter () from /usr/qt/3/lib/libqt-mt.so.3
#22 0xb6ae751b in QWidget::~QWidget () from /usr/qt/3/lib/libqt-mt.so.3
#23 0xb6ae79ab in QWidget::~QWidget () from /usr/qt/3/lib/libqt-mt.so.3
#24 0xb6ba3c20 in QMainWindow::~QMainWindow ()
   from /usr/qt/3/lib/libqt-mt.so.3
#25 0xb739712d in ~KMainWindow (this=0x84d4430, __vtt_parm=0xb7efc200)
    at kmainwindow.cpp:322
#26 0xb7e745a2 in ~EditorWindow (this=0x84d4430, __vtt_parm=0xb7efc1fc)
    at editorwindow.cpp:139
#27 0xb7e79d4e in ~ImageWindow (this=0x84d4430) at imagewindow.cpp:218
#28 0xb6ae5ee7 in QWidget::close () from /usr/qt/3/lib/libqt-mt.so.3
#29 0xb7cce898 in ~DigikamApp (this=0x81871f8) at digikamapp.cpp:192
#30 0xb6aae240 in QObject::event () from /usr/qt/3/lib/libqt-mt.so.3
#31 0xb6ae680c in QWidget::event () from /usr/qt/3/lib/libqt-mt.so.3
#32 0xb6b9f8c2 in QMainWindow::event () from /usr/qt/3/lib/libqt-mt.so.3
#33 0xb6a4ff17 in QApplication::internalNotify ()
   from /usr/qt/3/lib/libqt-mt.so.3
#34 0xb6a50a81 in QApplication::notify () from /usr/qt/3/lib/libqt-mt.so.3
#35 0xb7118a16 in KApplication::notify (this=0xbfe1f8e4, receiver=0x81871f8, 
    event=0x85c8de0) at kapplication.cpp:550
#36 0xb6a51643 in QApplication::sendPostedEvents ()
   from /usr/qt/3/lib/libqt-mt.so.3
#37 0xb6a66640 in QEventLoop::enterLoop () from /usr/qt/3/lib/libqt-mt.so.3
#38 0xb6a66446 in QEventLoop::exec () from /usr/qt/3/lib/libqt-mt.so.3
#39 0xb6a4f9af in QApplication::exec () from /usr/qt/3/lib/libqt-mt.so.3
#40 0x0804a3d4 in main (argc=7, argv=0xbfe1faf4) at main.cpp:269
Comment 1 caulier.gilles 2007-01-02 21:11:57 UTC
The crash appear in destructor of image properties side bar implementation. I cannot reproduce this one here of course. 

Can you test it using the current implementation form svn or 0.9.0 final release ?

Gilles Caulier
Comment 2 Dik Takken 2007-01-03 09:40:34 UTC
I can't reproduce either. I will upgrade to 0.9.0 final soon.
Comment 3 caulier.gilles 2007-01-03 12:46:03 UTC
Dik, this file can be closed ?

Gilles
Comment 4 Dik Takken 2007-01-03 21:42:17 UTC
If the bug cannot be traced from the backtrace, sure. Bad luck...
Comment 5 caulier.gilles 2007-01-03 22:11:23 UTC
Dik, 

give me a report when you will test with 0.9.0 or better the current implementation from svn.

Gilles
Comment 6 caulier.gilles 2007-04-20 14:34:01 UTC
Dik, What's news about this crash. It diseappear ?

Gilles
Comment 7 Arnd Baecker 2007-06-03 12:44:44 UTC
This bug seems to be non-reproducible anymore. I would suggest to 
close it (... sorry Dik)
Comment 8 caulier.gilles 2007-06-03 13:35:50 UTC
Fine for me. Closed.

Gilles