[Digikam-devel] Is this a digikam problem?

[Heiner Lamprecht]

Hi,

it's driving me crazy.  Last night, I reinstalled my system, now as
pure 32 bit, in the hope, that digikam is more stable.

But I still got a crash.  I'm not sure, if this is really a problem
in digikam, since the crash happens when writing debug information:

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1239894352 (LWP 13409)]
[New Thread -1251255392 (LWP 13421)]
[KCrash handler]
#6  0xb61fd8fa in strcmp () from /lib/libc.so.6
#7  0xb707f741 in QMapPrivate<KEntryKey, KEntry>::find ()
   from /opt/kde3/lib/libkdecore.so.4
#8  0xb6fa4ca9 in KConfig::lookupData () from /opt/kde3/lib/libkdecore.so.4
#9  0xb6feeb6d in KConfigBase::readEntryUtf8 ()
   from /opt/kde3/lib/libkdecore.so.4
#10 0xb6ff1639 in KConfigBase::readNumEntry ()
   from /opt/kde3/lib/libkdecore.so.4
#11 0xb6ff2b0b in KConfigBase::readNumEntry ()
   from /opt/kde3/lib/libkdecore.so.4
#12 0xb6ff2ecb in kdbgstream::flush () from /opt/kde3/lib/libkdecore.so.4
#13 0xb7cde7db in kdbgstream::operator<< (this=0xbfc3d790,
    string=0xb7f1cc80 "\n") at /opt/kde3/include/kdebug.h:232
#14 0xb7cde811 in endl (s=@0xbfc3d790) at /opt/kde3/include/kdebug.h:430
#15 0xb7cdab89 in kdbgstream::operator<< (this=0xbfc3d790,
    f=0xb7cde7ea <endl(kdbgstream&)>) at /opt/kde3/include/kdebug.h:260
#16 0xb7ebfd1f in Digikam::IccTransform::apply (this=0xbfc3da84,
    image=@0xbfc3d8f0)
    at /work/heiner/Develop/digikam/unstable/graphics/digikam/libs/dimg/filters/icctransform.cpp:247
#17 0xb7ed47e4 in Digikam::DImg::convertToPixmap (this=0xd66e6c0,
    monitorICCtrans=0xbfc3da84)
    at /work/heiner/Develop/digikam/unstable/graphics/digikam/libs/dimg/dimg.cpp:1207
#18 0xb7eeeff2 in Digikam::ImageIface::paint (this=0xd66e648,
    device=0xd66e870, x=0, y=0, w=360, h=240)
    at /work/heiner/Develop/digikam/unstable/graphics/digikam/utilities/imageeditor/editor/imageiface.cpp:361
#19 0xb7e11bd1 in Digikam::ImagePanIconWidget::updatePixmap (this=0xd66e428)
    at /work/heiner/Develop/digikam/unstable/graphics/digikam/libs/widgets/imageplugins/imagepaniconwidget.cpp:194
#20 0xb7e12f27 in Digikam::ImagePanIconWidget::mouseMoveEvent (this=0xd66e428,
    e=0xbfc3e1d4)
    at /work/heiner/Develop/digikam/unstable/graphics/digikam/libs/widgets/imageplugins/imagepaniconwidget.cpp:316



    Heiner

--
    heiner at heiner-lamprecht dot net    GnuPG - Key: 9859E373
  Fingerprint:  3770 7947 F917 94EF 8717 BADB 0139 7554 9859 E373
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-2]

Heiner,

The crash arrive when you use an image plugin with the screen color management
option enabled. Right ?

Here, i have 6 computers (32 bits) where i can run digikam without problem,
but with this option enable.

Perhaps something is missing in screen color management part, especially if
you trying to use an unadapted color profile.

If you have used this option, please try again to toggle off.

Gilles

> Hi,
>
> it's driving me crazy.  Last night, I reinstalled my system, now as
> pure 32 bit, in the hope, that digikam is more stable.
>
> But I still got a crash.  I'm not sure, if this is really a problem
> in digikam, since the crash happens when writing debug information:
>
> Using host libthread_db library "/lib/libthread_db.so.1".
> [Thread debugging using libthread_db enabled]
> [New Thread -1239894352 (LWP 13409)]
> [New Thread -1251255392 (LWP 13421)]
> [KCrash handler]
> #6  0xb61fd8fa in strcmp () from /lib/libc.so.6
> #7  0xb707f741 in QMapPrivate<KEntryKey, KEntry>::find ()
>    from /opt/kde3/lib/libkdecore.so.4
> #8  0xb6fa4ca9 in KConfig::lookupData () from /opt/kde3/lib/libkdecore.so.4
> #9  0xb6feeb6d in KConfigBase::readEntryUtf8 ()
>    from /opt/kde3/lib/libkdecore.so.4
> #10 0xb6ff1639 in KConfigBase::readNumEntry ()
>    from /opt/kde3/lib/libkdecore.so.4
> #11 0xb6ff2b0b in KConfigBase::readNumEntry ()
>    from /opt/kde3/lib/libkdecore.so.4
> #12 0xb6ff2ecb in kdbgstream::flush () from /opt/kde3/lib/libkdecore.so.4
> #13 0xb7cde7db in kdbgstream::operator<< (this=0xbfc3d790,
>     string=0xb7f1cc80 "\n") at /opt/kde3/include/kdebug.h:232
> #14 0xb7cde811 in endl (s=@0xbfc3d790) at /opt/kde3/include/kdebug.h:430
> #15 0xb7cdab89 in kdbgstream::operator<< (this=0xbfc3d790,
>     f=0xb7cde7ea <endl(kdbgstream&)>) at /opt/kde3/include/kdebug.h:260
> #16 0xb7ebfd1f in Digikam::IccTransform::apply (this=0xbfc3da84,
>     image=@0xbfc3d8f0)
>     at
> /work/heiner/Develop/digikam/unstable/graphics/digikam/libs/dimg/filters/ic
>ctransform.cpp:247 #17 0xb7ed47e4 in Digikam::DImg::convertToPixmap
> (this=0xd66e6c0,
>     monitorICCtrans=0xbfc3da84)
>     at
> /work/heiner/Develop/digikam/unstable/graphics/digikam/libs/dimg/dimg.cpp:1
>207 #18 0xb7eeeff2 in Digikam::ImageIface::paint (this=0xd66e648,
>     device=0xd66e870, x=0, y=0, w=360, h=240)
>     at
> /work/heiner/Develop/digikam/unstable/graphics/digikam/utilities/imageedito
>r/editor/imageiface.cpp:361 #19 0xb7e11bd1 in
> Digikam::ImagePanIconWidget::updatePixmap (this=0xd66e428) at
> /work/heiner/Develop/digikam/unstable/graphics/digikam/libs/widgets/imagepl
>ugins/imagepaniconwidget.cpp:194 #20 0xb7e12f27 in
> Digikam::ImagePanIconWidget::mouseMoveEvent (this=0xd66e428, e=0xbfc3e1d4)
>     at
> /work/heiner/Develop/digikam/unstable/graphics/digikam/libs/widgets/imagepl
>ugins/imagepaniconwidget.cpp:316
>
>
>
>     Heiner

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Heiner Lamprecht]

Hi Gilles,

On Friday 25 August 2006 12:42, Gilles Caulier wrote:
> Heiner,
>
> The crash arrive when you use an image plugin with the screen
> color management option enabled. Right ?

Yes.

On console, I get some warning regularly:

digikam: intent: 0
digikam: input profile: default no alpha
lcms: Error #12288; Input profile is operating on wrong colorspace
digikam: [bool Digikam::IccTransform::apply(Digikam::DImg&)] LCMS
internal error: cannot create a color transform instance

> Perhaps something is missing in screen color management part,
> especially if you trying to use an unadapted color profile.

Hm.  I'm not enough a developer.  But why does the crash than happen
while writing "\n" to stderr?

> If you have used this option, please try again to toggle off.

See below for the result ;-(

What's going wrong here?  I'm using digikam for quite some months now
and must say, that it is a great application.  And even though it is
still called 0.9, it's very stable.

But now I bought a new maschine and installed Suse 10.1, and I'm
able to use digikam for more than 10 minutes.  Don't get me wrong.  I'm
very much willing to do what I can to help making digikam stable.  But
I have no clue of the reason might be.


Current backtrace:

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1240475984 (LWP 17639)]
[New Thread -1243444320 (LWP 17661)]
[New Thread -1251837024 (LWP 17651)]
0xffffe410 in __kernel_vsyscall ()
#0  0xffffe410 in __kernel_vsyscall ()
#1  0xb61cf18e in __lll_mutex_lock_wait () from /lib/libc.so.6
#2  0xb616dd81 in _L_mutex_lock_4119 () from /lib/libc.so.6
#3  0xb6d5b838 in ?? () from /usr/lib/qt3/lib/libqt-mt.so.3
#4  0x080b05a8 in ?? ()
#5  0xb632fff4 in ?? () from /usr/lib/libstdc++.so.6
#6  0x0865ad40 in ?? ()
#7  0x085ad9a8 in ?? ()
#8  0xbf9a1878 in ?? ()
#9  0xb6308e51 in operator delete () from /usr/lib/libstdc++.so.6
#10 0xb6308e51 in operator delete () from /usr/lib/libstdc++.so.6
#11 0xb6ba767d in QGList::removeRef () from /usr/lib/qt3/lib/libqt-mt.so.3
#12 0xb6893828 in QApplication::sendPostedEvents ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#13 0xb6893a16 in QApplication::sendPostedEvents ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#14 0xb6841567 in QEventLoop::processEvents ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#15 0xb68a8ce8 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3
#16 0xb68919ef in QApplication::enter_loop ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#17 0xb6a774d5 in QDialog::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#18 0xb3216280 in ImagePlugin_Refocus::slotRefocus (this=0x858ba10)
    at /work/heiner/Develop/digikam/unstable/graphics/digikamimageplugins/refocus/imageplugin_refocus.cpp:67
#19 0xb32162f1 in ImagePlugin_Refocus::qt_invoke (this=0x858ba10, _id=2,
    _o=0xbf9a1c78)
    at /work/heiner/Develop/digikam/unstable/graphics/digikamimageplugins/refocus/imageplugin_refocus.moc:82
#20 0xb68f0edd in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#21 0xb68f1b3d in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#22 0xb71b7a69 in KAction::activated () from /opt/kde3/lib/libkdeui.so.4
#23 0xb71ecea2 in KAction::slotActivated () from /opt/kde3/lib/libkdeui.so.4
#24 0xb72da12d in KAction::slotPopupActivated ()
   from /opt/kde3/lib/libkdeui.so.4
#25 0xb72da3f1 in KAction::qt_invoke () from /opt/kde3/lib/libkdeui.so.4
#26 0xb68f0edd in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#27 0xb6c29a9e in QSignal::signal () from /usr/lib/qt3/lib/libqt-mt.so.3
#28 0xb690cf87 in QSignal::activate () from /usr/lib/qt3/lib/libqt-mt.so.3
#29 0xb69f85ea in QPopupMenu::mouseReleaseEvent ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#30 0xb71c0efe in KPopupMenu::mouseReleaseEvent ()
   from /opt/kde3/lib/libkdeui.so.4
#31 0xb6929c00 in QWidget::event () from /usr/lib/qt3/lib/libqt-mt.so.3
#32 0xb6891ec7 in QApplication::internalNotify ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#33 0xb6892dfb in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3
#34 0xb6fd5963 in KApplication::notify () from /opt/kde3/lib/libkdecore.so.4
#35 0xb68326ae in QETWidget::translateMouseEvent ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#36 0xb6830fa6 in QApplication::x11ProcessEvent ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#37 0xb68415ea in QEventLoop::processEvents ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#38 0xb68a8ce8 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3
#39 0xb68a8b7e in QEventLoop::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#40 0xb6891a7f in QApplication::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#41 0x0804ab2c in main (argc=-1209189940, argv=0x22)
    at /work/heiner/Develop/digikam/unstable/graphics/digikam/digikam/main.cpp:273


--
    heiner at heiner-lamprecht dot net    GnuPG - Key: 9859E373
  Fingerprint:  3770 7947 F917 94EF 8717 BADB 0139 7554 9859 E373
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-2]

On Friday 25 August 2006 13:34, Heiner Lamprecht wrote:

> Hi Gilles,
>
> On Friday 25 August 2006 12:42, Gilles Caulier wrote:
> > Heiner,
> >
> > The crash arrive when you use an image plugin with the screen
> > color management option enabled. Right ?
>
> Yes.
>
> On console, I get some warning regularly:
>
> digikam: intent: 0
> digikam: input profile: default no alpha
> lcms: Error #12288; Input profile is operating on wrong colorspace
> digikam: [bool Digikam::IccTransform::apply(Digikam::DImg&)] LCMS
> internal error: cannot create a color transform instance
>

This is important ! When screen color management is disabled, these errors
disapear ?

> > Perhaps something is missing in screen color management part,
> > especially if you trying to use an unadapted color profile.
>
> Hm.  I'm not enough a developer.  But why does the crash than happen
> while writing "\n" to stderr?
>
> > If you have used this option, please try again to toggle off.
>
> See below for the result ;-(
>
> What's going wrong here?  I'm using digikam for quite some months now
> and must say, that it is a great application.  And even though it is
> still called 0.9, it's very stable.
>
> But now I bought a new maschine and installed Suse 10.1,

Me too. I use Suse 10.1 and Mandriva 2006 to test and develop...

> and I'm
> able to use digikam for more than 10 minutes.  Don't get me wrong.  I'm
> very much willing to do what I can to help making digikam stable.  But
> I have no clue of the reason might be.
>
>
> Current backtrace:
>
> Using host libthread_db library "/lib/libthread_db.so.1".
> [Thread debugging using libthread_db enabled]
> [New Thread -1240475984 (LWP 17639)]
> [New Thread -1243444320 (LWP 17661)]
> [New Thread -1251837024 (LWP 17651)]
> 0xffffe410 in __kernel_vsyscall ()
> #0  0xffffe410 in __kernel_vsyscall ()
> #1  0xb61cf18e in __lll_mutex_lock_wait () from /lib/libc.so.6
> #2  0xb616dd81 in _L_mutex_lock_4119 () from /lib/libc.so.6
> #3  0xb6d5b838 in ?? () from /usr/lib/qt3/lib/libqt-mt.so.3
> #4  0x080b05a8 in ?? ()
> #5  0xb632fff4 in ?? () from /usr/lib/libstdc++.so.6
> #6  0x0865ad40 in ?? ()
> #7  0x085ad9a8 in ?? ()
> #8  0xbf9a1878 in ?? ()
> #9  0xb6308e51 in operator delete () from /usr/lib/libstdc++.so.6
> #10 0xb6308e51 in operator delete () from /usr/lib/libstdc++.so.6
> #11 0xb6ba767d in QGList::removeRef () from /usr/lib/qt3/lib/libqt-mt.so.3
> #12 0xb6893828 in QApplication::sendPostedEvents ()
>    from /usr/lib/qt3/lib/libqt-mt.so.3
> #13 0xb6893a16 in QApplication::sendPostedEvents ()
>    from /usr/lib/qt3/lib/libqt-mt.so.3
> #14 0xb6841567 in QEventLoop::processEvents ()
>    from /usr/lib/qt3/lib/libqt-mt.so.3
> #15 0xb68a8ce8 in QEventLoop::enterLoop () from
> /usr/lib/qt3/lib/libqt-mt.so.3 #16 0xb68919ef in QApplication::enter_loop
> ()
>    from /usr/lib/qt3/lib/libqt-mt.so.3
> #17 0xb6a774d5 in QDialog::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
> #18 0xb3216280 in ImagePlugin_Refocus::slotRefocus (this=0x858ba10)
>     at
> /work/heiner/Develop/digikam/unstable/graphics/digikamimageplugins/refocus/
>imageplugin_refocus.cpp:67 #19 0xb32162f1 in ImagePlugin_Refocus::qt_invoke
> (this=0x858ba10, _id=2, _o=0xbf9a1c78)
>     at
> /work/heiner/Develop/digikam/unstable/graphics/digikamimageplugins/refocus/
>imageplugin_refocus.moc:82 #20 0xb68f0edd in QObject::activate_signal ()
>    from /usr/lib/qt3/lib/libqt-mt.so.3
> #21 0xb68f1b3d in QObject::activate_signal ()
>    from /usr/lib/qt3/lib/libqt-mt.so.3
> #22 0xb71b7a69 in KAction::activated () from /opt/kde3/lib/libkdeui.so.4
> #23 0xb71ecea2 in KAction::slotActivated () from
> /opt/kde3/lib/libkdeui.so.4 #24 0xb72da12d in KAction::slotPopupActivated
> ()
>    from /opt/kde3/lib/libkdeui.so.4
> #25 0xb72da3f1 in KAction::qt_invoke () from /opt/kde3/lib/libkdeui.so.4
> #26 0xb68f0edd in QObject::activate_signal ()
>    from /usr/lib/qt3/lib/libqt-mt.so.3
> #27 0xb6c29a9e in QSignal::signal () from /usr/lib/qt3/lib/libqt-mt.so.3
> #28 0xb690cf87 in QSignal::activate () from /usr/lib/qt3/lib/libqt-mt.so.3
> #29 0xb69f85ea in QPopupMenu::mouseReleaseEvent ()
>    from /usr/lib/qt3/lib/libqt-mt.so.3
> #30 0xb71c0efe in KPopupMenu::mouseReleaseEvent ()
>    from /opt/kde3/lib/libkdeui.so.4
> #31 0xb6929c00 in QWidget::event () from /usr/lib/qt3/lib/libqt-mt.so.3
> #32 0xb6891ec7 in QApplication::internalNotify ()
>    from /usr/lib/qt3/lib/libqt-mt.so.3
> #33 0xb6892dfb in QApplication::notify () from
> /usr/lib/qt3/lib/libqt-mt.so.3 #34 0xb6fd5963 in KApplication::notify ()
> from /opt/kde3/lib/libkdecore.so.4 #35 0xb68326ae in
> QETWidget::translateMouseEvent ()
>    from /usr/lib/qt3/lib/libqt-mt.so.3
> #36 0xb6830fa6 in QApplication::x11ProcessEvent ()
>    from /usr/lib/qt3/lib/libqt-mt.so.3
> #37 0xb68415ea in QEventLoop::processEvents ()
>    from /usr/lib/qt3/lib/libqt-mt.so.3
> #38 0xb68a8ce8 in QEventLoop::enterLoop () from
> /usr/lib/qt3/lib/libqt-mt.so.3 #39 0xb68a8b7e in QEventLoop::exec () from
> /usr/lib/qt3/lib/libqt-mt.so.3 #40 0xb6891a7f in QApplication::exec () from
> /usr/lib/qt3/lib/libqt-mt.so.3 #41 0x0804ab2c in main (argc=-1209189940,
> argv=0x22)
>     at
> /work/heiner/Develop/digikam/unstable/graphics/digikam/digikam/main.cpp:273

Hum, sound like http://bugs.kde.org/show_bug.cgi?id=132649       

Are you running digiKam in gdb to get this backtrace ?

Can you try to get a valgrind backtrace using the command line describe to the
end of HACKING file from svn ?

Gilles
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Heiner Lamprecht]

Hi Gilles,

On Friday 25 August 2006 13:47, Gilles Caulier wrote:

> On Friday 25 August 2006 13:34, Heiner Lamprecht wrote:
> > Hi Gilles,
> >
> > On Friday 25 August 2006 12:42, Gilles Caulier wrote:
> > > Heiner,
> > >
> > > The crash arrive when you use an image plugin with the screen
> > > color management option enabled. Right ?
> >
> > Yes.
> >
> > On console, I get some warning regularly:
> >
> > digikam: intent: 0
> > digikam: input profile: default no alpha
> > lcms: Error #12288; Input profile is operating on wrong
> > colorspace digikam: [bool
> > Digikam::IccTransform::apply(Digikam::DImg&)] LCMS internal
> > error: cannot create a color transform instance
>
> This is important ! When screen color management is disabled,
> these errors disapear ?

Yes, they don't appear anymore.

> Hum, sound like http://bugs.kde.org/show_bug.cgi?id=132649
>
> Are you running digiKam in gdb to get this backtrace ?

No.  I only configured it with --enable-debug=full.  And that's what
the KDE crashhandler shows me :-)

> Can you try to get a valgrind backtrace using the command line
> describe to the end of HACKING file from svn ?

Maybe tonight.

During the last hour, I hopefully made a big step forward:  I
disabled hyperthreading in the BIOS.  And since than, digikam seems
to run stable.  I'm not 100% sure, because the crashes were hard to
reproduce.  But I was able to use (and stress) digikam for a much
longer period then before :-)  Both with CMS disabled and enabled.

Now I will first prepare some printouts (what I wanted to do since
Monday ...).  If digikam runs stable through this, I'll retry the
same under 64bit.  When I'm sure, that the hyperthreading was the
reason, I'll switch it on again to get some more debugging info.


    Heiner

--
    heiner at heiner-lamprecht dot net    GnuPG - Key: 9859E373
  Fingerprint:  3770 7947 F917 94EF 8717 BADB 0139 7554 9859 E373
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel