------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=133026 Summary: crashes on systems using hyperthreading Product: digikam Version: 0.9.0-svn Platform: SuSE RPMs OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: digikam-devel kde org ReportedBy: heiner heiner-lamprecht net Version: 0.9.0-svn (using KDE KDE 3.5.4) Installed from: SuSE RPMs Compiler: gcc version 4.0.2 OS: Linux When hyperthreading is enabled in the BIOS, digikam crashes often and in several situations, eg. when loading images or editing them in IE. There is no special way to reproduce the crashes. I assume, there are some problems in communication between threads. When hyperthreading is disabled, dikigam runs rocksolid. System: SuSE Linux 10.1 uname -a: Linux tharbad 2.6.16.21-0.13-smp #1 SMP Mon Jul 17 17:22:44 UTC 2006 x86_64 x86_64 x86_64 GNU/Linux See #132649 for backtraces. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=133026 ------- Additional Comments From aironmail gmail com 2006-08-26 14:55 ------- That's strange. My system is always using hiperthreading, and the 0.9svn doesn't seem to experiment any problem related to the hiperthreading. To me, with a normal use, it's even hard to crash. Could it be that you have a hardware problem or some library conflict? _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Heiner Lamprecht
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=133026 aironmail gmail com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aironmail gmail com _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Heiner Lamprecht
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=133026 ------- Additional Comments From heiner heiner-lamprecht net 2006-08-26 15:05 ------- Indeed, it's strange. But it's the only explanation I found. When I go to the BIOS and enable hyperthreading, digikam is unusable. When I disable it, I can work. All other applications run without any problems. So, for me, a hardware problem is unlikely. Library conflict? Maybe, but what library should I look for? _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Heiner Lamprecht
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=133026 caulier.gilles free fr changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW everconfirmed|0 |1 ------- Additional Comments From caulier.gilles free fr 2006-08-27 09:38 ------- Ii confirm this problem. tested on 6 computers here. 3 without using hyperthreading, 3 with hyperthreading. Marcel, something is missing in compilation options ? Gilles _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Heiner Lamprecht
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=133026 ------- Additional Comments From caulier.gilles free fr 2006-08-27 20:52 ------- I can confirm this bung indeep. Today i have corrected over 100 RAW picture in my computer with HT disable : no crash ! If HT is enable digiKam crash a lot of time, especially with al image plugins with use the image filter QThread class : http://websvn.kde.org/trunk/extragear/graphics/digikam/libs/dimg/filters/dimgthreadedfilter.cpp Marcel, are you sure than your last changes in this code is clean ? Note : just a link in Qt ML : http://lists.trolltech.com/qt-interest/2005-05/thread00815-0.html Gilles _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Heiner Lamprecht
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=133026 ------- Additional Comments From caulier.gilles free fr 2006-08-27 20:55 ------- *** Bug 132649 has been marked as a duplicate of this bug. *** _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Heiner Lamprecht
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=133026 ------- Additional Comments From marcel.wiesweg gmx de 2006-08-27 23:23 ------- Is it always the same backtrace as posted in 132649? Or are there other bts? Unfortunately I don't have a hyperthreading-capable or dual core machine anywhere near, my Pentium M doesnt do it. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Heiner Lamprecht
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=133026 ------- Additional Comments From aironmail gmail com 2006-08-28 00:29 ------- I've been reading the backtrace of that issue, I've seen something strange to me: /lib64/libthread_db.so.1. /lib64/libc.so.6 What? lib64? Linux threads (glibc) for a 64 bits machine in a pentium 4? I've never seen that for a 32 bits distro. If I can help doing some testing in my machine just tell me. I have a pentium4 with HT enabled (Gentoo), using the kernel 2.6.17. I don't know which are exactly the actions that I have to do to try to crash it, because I repeat, to me it works fine. I haven't tried raw images. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Heiner Lamprecht
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=133026 ------- Additional Comments From caulier.gilles free fr 2006-08-28 07:41 ------- SVN commit 577999 by cgilles: digikam from trunk : threaded Image plugin dialogs : Change test to check if computation is already in progress to prevent dupplicate event from gui Heiner, please check if this fix improve the stability with MT on your system. Thanks in advance CCBUGS: 133026 M +1 -2 ctrlpaneldlg.cpp M +1 -2 imageguidedlg.cpp --- trunk/extragear/graphics/digikam/libs/dialogs/ctrlpaneldlg.cpp #577998:577999 @ -287,8 +287,7 @ void CtrlPanelDlg::slotEffect() { // Computation already in process. - if (d->currentRenderingMode == CtrlPanelDlgPriv::PreviewRendering || - d->currentRenderingMode == CtrlPanelDlgPriv::FinalRendering) + if (d->currentRenderingMode != CtrlPanelDlgPriv::NoneRendering) return; d->currentRenderingMode = CtrlPanelDlgPriv::PreviewRendering; --- trunk/extragear/graphics/digikam/libs/dialogs/imageguidedlg.cpp #577998:577999 @ -427,8 +427,7 @ void ImageGuideDlg::slotEffect() { // Computation already in process. - if (d->currentRenderingMode == ImageGuideDlgPriv::PreviewRendering || - d->currentRenderingMode == ImageGuideDlgPriv::FinalRendering) + if (d->currentRenderingMode != ImageGuideDlgPriv::NoneRendering) return; d->currentRenderingMode = ImageGuideDlgPriv::PreviewRendering; _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Heiner Lamprecht
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=133026 ------- Additional Comments From caulier.gilles free fr 2006-08-28 07:53 ------- Antonio, The crash is not relevant of 8 or 16 bits color depth images. The crash appear just before to update the preview in plugin dialogs, for example when you change the focus area with Noise Reduction or Refocus tool. I can reproduce also this problem with Free Rotation tool. It another common dialog implementation... In both, the image filter algorithm is forked to a separate thread to unfreeze gui and speed up computation (with HT, we using the second processor to compute algorithms). Note : This is not the case of all "Color" image plugins, like BCG, B&W, WB, or RGB correction tools for example, witch use another one common dialog. This one is not yet ported to use a separate thread with algorithm. I suspect multi-events from gui witch start more than one computation threads at the same time and of course crash digiKam when computations are done (multi-results witch update preview). I don't know why this side effect appear with HT only. Marcel, if you have some ideas... Gilles _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Heiner Lamprecht
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=133026 ------- Additional Comments From heiner heiner-lamprecht net 2006-08-28 10:36 ------- Gilles, I've checked your changes, but it doesn't look like it solved the issue. On the 32bit version, I had two crashes within 15 minutes. I'm not sure, if multi-events are realy the reason. The crashes happen, eg. when I move the preview (the rectangle in the small complete view in the upper right) in a filter dialog. But that's not possible, while a computation is running. Backtrace #1: Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1239882064 (LWP 23218)] [New Thread -1251243104 (LWP 23230)] [KCrash handler] #6 0xb61faa22 in malloc_consolidate () from /lib/libc.so.6 #7 0xb61fc679 in _int_malloc () from /lib/libc.so.6 #8 0xb61fe206 in malloc () from /lib/libc.so.6 #9 0xb6951716 in QImage::QImage () from /usr/lib/qt3/lib/libqt-mt.so.3 #10 0xb7ede9e3 in Digikam::DImg::convertToPixmap (this=0xbfe8a350) at /work/heiner/Develop/digikam/unstable/graphics/digikam/libs/dimg/dimg.cpp:1174 #11 0xb7edebaa in Digikam::DImg::convertToPixmap (this=0xabdf1e98, monitorICCtrans=0xbfe8a4e4) at /work/heiner/Develop/digikam/unstable/graphics/digikam/libs/dimg/dimg.cpp:1210 #12 0xb7ef93a6 in Digikam::ImageIface::paint (this=0xabdf1e20, device=0xabef1e68, x=0, y=0, w=360, h=240) at /work/heiner/Develop/digikam/unstable/graphics/digikam/utilities/imageeditor/editor/imageiface.cpp:361 #13 0xb7e18741 in Digikam::ImagePanIconWidget::updatePixmap (this=0xae9f1e10) at /work/heiner/Develop/digikam/unstable/graphics/digikam/libs/widgets/imageplugins/imagepaniconwidget.cpp:194 #14 0xb7e19a97 in Digikam::ImagePanIconWidget::mouseMoveEvent ( this=0xae9f1e10, e=0xbfe8ac34) at /work/heiner/Develop/digikam/unstable/graphics/digikam/libs/widgets/imageplugins/imagepaniconwidget.cpp:316 #15 0xb69babc4 in QWidget::event () from /usr/lib/qt3/lib/libqt-mt.so.3 #16 0xb6922ec7 in QApplication::internalNotify () from /usr/lib/qt3/lib/libqt-mt.so.3 #17 0xb6923dfb in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3 #18 0xb7066963 in KApplication::notify () from /opt/kde3/lib/libkdecore.so.4 #19 0xb68c2dd2 in QETWidget::translateMouseEvent () from /usr/lib/qt3/lib/libqt-mt.so.3 #20 0xb68c1fa6 in QApplication::x11ProcessEvent () from /usr/lib/qt3/lib/libqt-mt.so.3 #21 0xb68d25ea in QEventLoop::processEvents () from /usr/lib/qt3/lib/libqt-mt.so.3 #22 0xb6939ce8 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3 #23 0xb69229ef in QApplication::enter_loop () from /usr/lib/qt3/lib/libqt-mt.so.3 #24 0xb6b084d5 in QDialog::exec () from /usr/lib/qt3/lib/libqt-mt.so.3 #25 0xb32a7280 in ImagePlugin_Refocus::slotRefocus (this=0x858f0e8) at /work/heiner/Develop/digikam/unstable/graphics/digikamimageplugins/refocus/imageplugin_refocus.cpp:67 #26 0xb32a72f1 in ImagePlugin_Refocus::qt_invoke (this=0x858f0e8, _id=2, _o=0xbfe8b158) at /work/heiner/Develop/digikam/unstable/graphics/digikamimageplugins/refocus/imageplugin_refocus.moc:82 #27 0xb6981edd in QObject::activate_signal () from /usr/lib/qt3/lib/libqt-mt.so.3 #28 0xb6982b3d in QObject::activate_signal () from /usr/lib/qt3/lib/libqt-mt.so.3 #29 0xb7248a69 in KAction::activated () from /opt/kde3/lib/libkdeui.so.4 #30 0xb727dea2 in KAction::slotActivated () from /opt/kde3/lib/libkdeui.so.4 #31 0xb736b12d in KAction::slotPopupActivated () from /opt/kde3/lib/libkdeui.so.4 #32 0xb736b3f1 in KAction::qt_invoke () from /opt/kde3/lib/libkdeui.so.4 #33 0xb6981edd in QObject::activate_signal () from /usr/lib/qt3/lib/libqt-mt.so.3 #34 0xb6cbaa9e in QSignal::signal () from /usr/lib/qt3/lib/libqt-mt.so.3 #35 0xb699df87 in QSignal::activate () from /usr/lib/qt3/lib/libqt-mt.so.3 #36 0xb6a895ea in QPopupMenu::mouseReleaseEvent () from /usr/lib/qt3/lib/libqt-mt.so.3 #37 0xb7251efe in KPopupMenu::mouseReleaseEvent () from /opt/kde3/lib/libkdeui.so.4 #38 0xb69bac00 in QWidget::event () from /usr/lib/qt3/lib/libqt-mt.so.3 #39 0xb6922ec7 in QApplication::internalNotify () from /usr/lib/qt3/lib/libqt-mt.so.3 #40 0xb6923dfb in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3 #41 0xb7066963 in KApplication::notify () from /opt/kde3/lib/libkdecore.so.4 #42 0xb68c36ae in QETWidget::translateMouseEvent () from /usr/lib/qt3/lib/libqt-mt.so.3 #43 0xb68c1fa6 in QApplication::x11ProcessEvent () from /usr/lib/qt3/lib/libqt-mt.so.3 #44 0xb68d25ea in QEventLoop::processEvents () from /usr/lib/qt3/lib/libqt-mt.so.3 #45 0xb6939ce8 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3 #46 0xb6939b7e in QEventLoop::exec () from /usr/lib/qt3/lib/libqt-mt.so.3 #47 0xb6922a7f in QApplication::exec () from /usr/lib/qt3/lib/libqt-mt.so.3 #48 0x0804ab2c in main (argc=-1208559796, argv=0x22) at /work/heiner/Develop/digikam/unstable/graphics/digikam/digikam/main.cpp:273 =========================================================================== Backtrace #2: Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1240082768 (LWP 23973)] [New Thread -1251443808 (LWP 24009)] [KCrash handler] #6 0xb61cf8fa in strcmp () from /lib/libc.so.6 #7 0xb7051741 in QMapPrivate<KEntryKey, KEntry>::find () from /opt/kde3/lib/libkdecore.so.4 #8 0xb6f76ca9 in KConfig::lookupData () from /opt/kde3/lib/libkdecore.so.4 #9 0xb6fc0b6d in KConfigBase::readEntryUtf8 () from /opt/kde3/lib/libkdecore.so.4 #10 0xb6fc3639 in KConfigBase::readNumEntry () from /opt/kde3/lib/libkdecore.so.4 #11 0xb6fc4b0b in KConfigBase::readNumEntry () from /opt/kde3/lib/libkdecore.so.4 #12 0xb6fc4ecb in kdbgstream::flush () from /opt/kde3/lib/libkdecore.so.4 #13 0xb7cb359b in kdbgstream::operator<< (this=0xbfcc9830, string=0xb7ef65a0 "\n") at /opt/kde3/include/kdebug.h:232 #14 0xb7cb35d1 in endl (s= 0xbfcc9830) at /opt/kde3/include/kdebug.h:430 #15 0xb7caf949 in kdbgstream::operator<< (this=0xbfcc9830, f=0xb7cb35aa <endl(kdbgstream&)>) at /opt/kde3/include/kdebug.h:260 #16 0xb7e990d3 in Digikam::IccTransform::apply (this=0xbfcc9b24, image= 0xbfcc9990) at /work/heiner/Develop/digikam/unstable/graphics/digikam/libs/dimg/filters/icctransform.cpp:247 #17 0xb7eadb98 in Digikam::DImg::convertToPixmap (this=0x860a4c8, monitorICCtrans=0xbfcc9b24) at /work/heiner/Develop/digikam/unstable/graphics/digikam/libs/dimg/dimg.cpp:1207 #18 0xb7ec83a6 in Digikam::ImageIface::paint (this=0x860a450, device=0x860a678, x=0, y=0, w=360, h=240) at /work/heiner/Develop/digikam/unstable/graphics/digikam/utilities/imageeditor/editor/imageiface.cpp:361 #19 0xb7de7741 in Digikam::ImagePanIconWidget::updatePixmap (this=0x860a230) at /work/heiner/Develop/digikam/unstable/graphics/digikam/libs/widgets/imageplugins/imagepaniconwidget.cpp:194 #20 0xb7de8a97 in Digikam::ImagePanIconWidget::mouseMoveEvent (this=0x860a230, e=0xbfcca274) at /work/heiner/Develop/digikam/unstable/graphics/digikam/libs/widgets/imageplugins/imagepaniconwidget.cpp:316 #21 0xb6989bc4 in QWidget::event () from /usr/lib/qt3/lib/libqt-mt.so.3 #22 0xb68f1ec7 in QApplication::internalNotify () from /usr/lib/qt3/lib/libqt-mt.so.3 #23 0xb68f2dfb in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3 #24 0xb7035963 in KApplication::notify () from /opt/kde3/lib/libkdecore.so.4 #25 0xb6891dd2 in QETWidget::translateMouseEvent () from /usr/lib/qt3/lib/libqt-mt.so.3 #26 0xb6890fa6 in QApplication::x11ProcessEvent () from /usr/lib/qt3/lib/libqt-mt.so.3 #27 0xb68a15ea in QEventLoop::processEvents () from /usr/lib/qt3/lib/libqt-mt.so.3 #28 0xb6908ce8 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3 #29 0xb68f19ef in QApplication::enter_loop () from /usr/lib/qt3/lib/libqt-mt.so.3 #30 0xb6ad74d5 in QDialog::exec () from /usr/lib/qt3/lib/libqt-mt.so.3 #31 0xb3276280 in ImagePlugin_Refocus::slotRefocus (this=0x858c3f0) at /work/heiner/Develop/digikam/unstable/graphics/digikamimageplugins/refocus/imageplugin_refocus.cpp:67 #32 0xb32762f1 in ImagePlugin_Refocus::qt_invoke (this=0x858c3f0, _id=2, _o=0xbfcca798) at /work/heiner/Develop/digikam/unstable/graphics/digikamimageplugins/refocus/imageplugin_refocus.moc:82 #33 0xb6950edd in QObject::activate_signal () from /usr/lib/qt3/lib/libqt-mt.so.3 #34 0xb6951b3d in QObject::activate_signal () from /usr/lib/qt3/lib/libqt-mt.so.3 #35 0xb7217a69 in KAction::activated () from /opt/kde3/lib/libkdeui.so.4 #36 0xb724cea2 in KAction::slotActivated () from /opt/kde3/lib/libkdeui.so.4 #37 0xb733a12d in KAction::slotPopupActivated () from /opt/kde3/lib/libkdeui.so.4 #38 0xb733a3f1 in KAction::qt_invoke () from /opt/kde3/lib/libkdeui.so.4 #39 0xb6950edd in QObject::activate_signal () from /usr/lib/qt3/lib/libqt-mt.so.3 #40 0xb6c89a9e in QSignal::signal () from /usr/lib/qt3/lib/libqt-mt.so.3 #41 0xb696cf87 in QSignal::activate () from /usr/lib/qt3/lib/libqt-mt.so.3 #42 0xb6a585ea in QPopupMenu::mouseReleaseEvent () from /usr/lib/qt3/lib/libqt-mt.so.3 #43 0xb7220efe in KPopupMenu::mouseReleaseEvent () from /opt/kde3/lib/libkdeui.so.4 #44 0xb6989c00 in QWidget::event () from /usr/lib/qt3/lib/libqt-mt.so.3 #45 0xb68f1ec7 in QApplication::internalNotify () from /usr/lib/qt3/lib/libqt-mt.so.3 #46 0xb68f2dfb in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3 #47 0xb7035963 in KApplication::notify () from /opt/kde3/lib/libkdecore.so.4 #48 0xb68926ae in QETWidget::translateMouseEvent () from /usr/lib/qt3/lib/libqt-mt.so.3 #49 0xb6890fa6 in QApplication::x11ProcessEvent () from /usr/lib/qt3/lib/libqt-mt.so.3 #50 0xb68a15ea in QEventLoop::processEvents () from /usr/lib/qt3/lib/libqt-mt.so.3 #51 0xb6908ce8 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3 #52 0xb6908b7e in QEventLoop::exec () from /usr/lib/qt3/lib/libqt-mt.so.3 #53 0xb68f1a7f in QApplication::exec () from /usr/lib/qt3/lib/libqt-mt.so.3 #54 0x0804ab2c in main (argc=-1208760500, argv=0x22) at /work/heiner/Develop/digikam/unstable/graphics/digikam/digikam/main.cpp:273 _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Heiner Lamprecht
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=133026 ------- Additional Comments From caulier.gilles free fr 2006-08-28 10:44 ------- Heiner, The computation is started when you release the left mouse button (in the case of Refocus dialog) Is digiKam crash also when you move the preview content to change the focus area ? With the second backtrace, you have enabled screen Color Management. I recommend you to disable it for these investigaution, else we will cumulate the problem to solve. We will look this problem later. Gilles _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Heiner Lamprecht
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=133026 ------- Additional Comments From heiner heiner-lamprecht net 2006-08-28 10:51 ------- Gilles, IIRC, digikam never crashed while only moving the rectangle. Heiner _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Heiner Lamprecht
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=133026 ------- Additional Comments From heiner heiner-lamprecht net 2006-08-28 11:49 ------- Okay, I disabled CMS. Testing gave me two more backtraces. The first one occured when closing the application, the second again with refocus filter. Heiner ========================================================================== Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1240521040 (LWP 9701)] [KCrash handler] #6 0xd0b6b895 in ?? () #7 0xb6927e64 in QVariant::Private::clear () from /usr/lib/qt3/lib/libqt-mt.so.3 #8 0xb692842d in QVariant::Private::~Private () from /usr/lib/qt3/lib/libqt-mt.so.3 #9 0xb69285c5 in QVariant::~QVariant () from /usr/lib/qt3/lib/libqt-mt.so.3 #10 0xb7dd8b8a in ~QMapNode (this=0x82d2a00) at /usr/lib/qt3/include/qmap.h:84 #11 0xb7dd9834 in QMapPrivate<QString, QVariant>::clear (this=0x81c7158, p=0x82d2a00) at /usr/lib/qt3/include/qmap.h:490 #12 0xb7dd987c in QMapPrivate<QString, QVariant>::clear (this=0x81c7158) at /usr/lib/qt3/include/qmap.h:477 #13 0xb7dd98dd in ~QMapPrivate (this=0x81c7158) at /usr/lib/qt3/include/qmap.h:371 #14 0xb7dd9944 in ~QMap (this=0x8222988) at /usr/lib/qt3/include/qmap.h:644 #15 0xb7e44d94 in ~DImgPrivate (this=0x8222970) at /work/heiner/Develop/digikam/unstable/graphics/digikam/libs/dimg/dimgprivate.h:59 #16 0xb7e41ad2 in ~DImg (this=0x82c4f70) at /work/heiner/Develop/digikam/unstable/graphics/digikam/libs/dimg/dimg.cpp:103 #17 0xb7dbc986 in QCache<Digikam::DImg>::deleteItem (this=0x874d1a8, d=0x82c4f70) at /usr/lib/qt3/include/qcache.h:90 #18 0xb6b97ebf in QGCache::clear () from /usr/lib/qt3/lib/libqt-mt.so.3 #19 0xb7dbc8ef in QCache<Digikam::DImg>::clear (this=0x874d1a8) at /usr/lib/qt3/include/qcache.h:66 #20 0xb7dbcb01 in ~QCache (this=0x874d1a8) at /usr/lib/qt3/include/qcache.h:57 #21 0xb7dbcb6d in ~LoadingCachePriv (this=0x874d1a8) at /work/heiner/Develop/digikam/unstable/graphics/digikam/libs/threadimageio/loadingcache.cpp:28 #22 0xb7dbc567 in ~LoadingCache (this=0x86fa538) at /work/heiner/Develop/digikam/unstable/graphics/digikam/libs/threadimageio/loadingcache.cpp:65 #23 0xb7dbc5be in Digikam::LoadingCache::cleanUp () at /work/heiner/Develop/digikam/unstable/graphics/digikam/libs/threadimageio/loadingcache.cpp:50 #24 0xb7dbceb5 in Digikam::LoadingCacheInterface::cleanUp () at /work/heiner/Develop/digikam/unstable/graphics/digikam/libs/threadimageio/loadingcacheinterface.cpp:30 #25 0xb7c6c10e in ~DigikamApp (this=0x8117f70) at /work/heiner/Develop/digikam/unstable/graphics/digikam/digikam/digikamapp.cpp:189 #26 0xb68e58a8 in QObject::event () from /usr/lib/qt3/lib/libqt-mt.so.3 #27 0xb691e88c in QWidget::event () from /usr/lib/qt3/lib/libqt-mt.so.3 #28 0xb69d9982 in QMainWindow::event () from /usr/lib/qt3/lib/libqt-mt.so.3 #29 0xb6886ec7 in QApplication::internalNotify () from /usr/lib/qt3/lib/libqt-mt.so.3 #30 0xb6887cb9 in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3 #31 0xb6fca963 in KApplication::notify () from /opt/kde3/lib/libkdecore.so.4 #32 0xb6888880 in QApplication::sendPostedEvents () from /usr/lib/qt3/lib/libqt-mt.so.3 #33 0xb689dd79 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3 #34 0xb689db7e in QEventLoop::exec () from /usr/lib/qt3/lib/libqt-mt.so.3 #35 0xb6886a7f in QApplication::exec () from /usr/lib/qt3/lib/libqt-mt.so.3 #36 0x0804ab2c in main (argc=-1209198772, argv=0x22) at /work/heiner/Develop/digikam/unstable/graphics/digikam/digikam/main.cpp:273 ========================================================================== Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1240349008 (LWP 12501)] [New Thread -1243317344 (LWP 12944)] [New Thread -1251710048 (LWP 12579)] 0xffffe410 in __kernel_vsyscall () #0 0xffffe410 in __kernel_vsyscall () #1 0xb61dbd11 in ___newselect_nocancel () from /lib/libc.so.6 #2 0xb68603b6 in QEventLoop::processEvents () from /usr/lib/qt3/lib/libqt-mt.so.3 #3 0xb68c7ce8 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3 #4 0xb68b09ef in QApplication::enter_loop () from /usr/lib/qt3/lib/libqt-mt.so.3 #5 0xb6a964d5 in QDialog::exec () from /usr/lib/qt3/lib/libqt-mt.so.3 #6 0xb3235280 in ImagePlugin_Refocus::slotRefocus (this=0x858e400) at /work/heiner/Develop/digikam/unstable/graphics/digikamimageplugins/refocus/imageplugin_refocus.cpp:67 #7 0xb32352f1 in ImagePlugin_Refocus::qt_invoke (this=0x858e400, _id=2, _o=0xbfe5c2a8) at /work/heiner/Develop/digikam/unstable/graphics/digikamimageplugins/refocus/imageplugin_refocus.moc:82 #8 0xb690fedd in QObject::activate_signal () from /usr/lib/qt3/lib/libqt-mt.so.3 #9 0xb6910b3d in QObject::activate_signal () from /usr/lib/qt3/lib/libqt-mt.so.3 #10 0xb71d6a69 in KAction::activated () from /opt/kde3/lib/libkdeui.so.4 #11 0xb720bea2 in KAction::slotActivated () from /opt/kde3/lib/libkdeui.so.4 #12 0xb72f93df in KAction::qt_invoke () from /opt/kde3/lib/libkdeui.so.4 #13 0xb690fedd in QObject::activate_signal () from /usr/lib/qt3/lib/libqt-mt.so.3 #14 0xb6910b3d in QObject::activate_signal () from /usr/lib/qt3/lib/libqt-mt.so.3 #15 0xb6f0eb29 in KAccelPrivate::menuItemActivated () from /opt/kde3/lib/libkdecore.so.4 #16 0xb6f5e9d7 in KAccelPrivate::emitActivatedSignal () from /opt/kde3/lib/libkdecore.so.4 #17 0xb6fe9e39 in KAccelPrivate::eventFilter () from /opt/kde3/lib/libkdecore.so.4 #18 0xb690f7dc in QObject::activate_filters () from /usr/lib/qt3/lib/libqt-mt.so.3 #19 0xb690f84b in QObject::event () from /usr/lib/qt3/lib/libqt-mt.so.3 #20 0xb694888c in QWidget::event () from /usr/lib/qt3/lib/libqt-mt.so.3 #21 0xb6a03982 in QMainWindow::event () from /usr/lib/qt3/lib/libqt-mt.so.3 #22 0xb68b0ec7 in QApplication::internalNotify () from /usr/lib/qt3/lib/libqt-mt.so.3 #23 0xb68b2222 in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3 #24 0xb6ff4963 in KApplication::notify () from /opt/kde3/lib/libkdecore.so.4 #25 0xb6f6a722 in KAccelEventHandler::x11Event () from /opt/kde3/lib/libkdecore.so.4 #26 0xb6ff27ab in KApplication::x11EventFilter () from /opt/kde3/lib/libkdecore.so.4 #27 0xb683fdc4 in qt_x11EventFilter () from /usr/lib/qt3/lib/libqt-mt.so.3 #28 0xb684f733 in QApplication::x11ProcessEvent () from /usr/lib/qt3/lib/libqt-mt.so.3 #29 0xb68605ea in QEventLoop::processEvents () from /usr/lib/qt3/lib/libqt-mt.so.3 #30 0xb68c7ce8 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3 #31 0xb68c7b7e in QEventLoop::exec () from /usr/lib/qt3/lib/libqt-mt.so.3 #32 0xb68b0a7f in QApplication::exec () from /usr/lib/qt3/lib/libqt-mt.so.3 #33 0x0804ab2c in main (argc=-1209026740, argv=0x22) at /work/heiner/Develop/digikam/unstable/graphics/digikam/digikam/main.cpp:273 Last messages on console: digikam: Preview refocus started... digikam: Refocus::Start of computation... digikam: Refocus::Compute matrix... digikam: Refocus::Apply Matrix to image... digikam: Preview refocus completed... digikam: Refocus::End of computation !!! ... ( 2 s ) digikam: Preview refocus started... digikam: Refocus::Start of computation... KCrash: Application 'digikam' crashing... QSocketNotifier: invalid socket 19 and type 'Read', disabling... QSocketNotifier: invalid socket 17 and type 'Read', disabling... QSocketNotifier: invalid socket 14 and type 'Read', disabling... QSocketNotifier: invalid socket 9 and type 'Read', disabling... QSocketNotifier: invalid socket 18 and type 'Read', disabling... QSocketNotifier: invalid socket 11 and type 'Read', disabling... QSocketNotifier: invalid socket 15 and type 'Read', disabling... QSocketNotifier: invalid socket 6 and type 'Read', disabling... digikam: Fatal IO error: client killed _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Heiner Lamprecht
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=133026 ------- Additional Comments From marcel.wiesweg gmx de 2006-08-28 23:14 ------- Created an attachment (id=17537) --> (http://bugs.kde.org/attachment.cgi?id=17537&action=view) debug statements All these backtraces are strange and do not seem to be related to moving the rectangle in the refocus plugin...I dont trust bts too much. I have created a patch which adds a lot more bts to some relevant parts (for crashing when moving the focus rectangle in the Refocus plugin), perhaps we can find the location where the crash happens. That's the only idea I currently have. Btw, are all those plugins using the CtrlPanelDlg or is this not correlated? _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Heiner Lamprecht
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=133026 ------- Additional Comments From caulier.gilles free fr 2006-08-28 23:30 ------- Yes, all : refocus, unsharp mask, noise reduction etc... and also all plugins witch use imageguidedlg dialog implementation (free rotation for example) The both dialogs use the threaded image filter class. I'm sure, i can reproduce the problem here, on my wife's computer : PIV-3.2 Ghz, 500Mb with hyperthreading. I have seen that more cpu is speed, more the problem is reproductible. For example, at work, i have another PIV HT computer where i have decreased the cpu speed, and in this case, the crash is more difficult to reproduce. Of course, if i disable HT, the crash do not appear. I have tested under Mandriva 2005-2006 and Suse 10.1. The crash sound like an disynchronism, or something like that. Marcel, are you seen in amarok : there is a method to controling HT : http://websvn.kde.org/trunk/extragear/multimedia/amarok/src/app.cpp?rev=576765&view=auto ... look void App::fixHyperThreading() method... Gilles _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Heiner Lamprecht
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=133026 ------- Additional Comments From caulier.gilles free fr 2006-08-28 23:32 ------- Very intructive story from amarok : http://bugs.kde.org/show_bug.cgi?id=99199 Gilles _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Heiner Lamprecht
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=133026 ------- Additional Comments From gerhard kulzer net 2006-08-30 10:56 ------- It seems to me that the bug has been fixed. I stressed digiKam for 2 days now with the notorious plugins and it was rock-stable. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Heiner Lamprecht
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=133026 ------- Additional Comments From caulier.gilles free fr 2006-08-30 17:59 ------- Gerhard, Are you sure to haven't changed/updated something in your computer, like kernel or/and libc ? Friendly Gilles _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
Free forum by Nabble | Edit this page |