Bug 169830

Summary:	digiKam crashed when navigating large images
Product:	[Applications] digikam	Reporter:	Nathan <packingdaddy>
Component:	Database-Files	Assignee:	Digikam Developers <digikam-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	crash	CC:	caulier.gilles, packingdaddy
Priority:	NOR
Version:	0.9.3
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:	0.10.0
Sentry Crash Report:

Description Nathan 2008-08-26 03:17:11 UTC

Version:           0.9.3 (using KDE 4.0.5)
OS:                Linux
Installed from:    Ubuntu Packages

I had opened an image in digiKam (not the thumbnails, the larger version) and was navigating forward in the list.  Program crashed and back trace is attached.

Comment 1 Nathan 2008-08-26 03:17:44 UTC

[Thread debugging using libthread_db enabled]
[New Thread 0x7f55dbdb96f0 (LWP 20428)]
[New Thread 0x411aa950 (LWP 20451)]
[New Thread 0x419ab950 (LWP 20450)]
[KCrash handler]
#5  0x00007f55d973e105 in QString::unicode (this=0xc3aaaf)
    at ../include/qstring.h:656
#6  0x00007f55d9b1db16 in operator== (s1=@0xc3aaaf, s2=@0x7fffe3df2750)
    at tools/qstring.cpp:6474
#7  0x00007f55db72da0c in QValueListPrivate<QString>::contains (
    this=<value optimized out>, x=@0x7fffe3df2750)
    at /usr/share/qt3/include/qvaluelist.h:349
#8  0x00007f55db818dbd in Digikam::LoadingCache::customEvent (this=0x18e52c0)
    at /usr/share/qt3/include/qvaluelist.h:548
#9  0x00007f55d98140bd in QObject::event (this=0x18e52c0, e=0x1986710)
    at kernel/qobject.cpp:758
#10 0x00007f55d97ae33a in QApplication::internalNotify (this=0x7fffe3df3390, 
    receiver=0x18e52c0, e=0x1986710) at kernel/qapplication.cpp:2638
#11 0x00007f55d97b0093 in QApplication::notify (this=0x7fffe3df3390, 
    receiver=0x18e52c0, e=0x1986710) at kernel/qapplication.cpp:2361
#12 0x00007f55da21b40d in KApplication::notify (this=0x7fffe3df3390, 
    receiver=0x18e52c0, event=0x1986710)
    at /build/buildd/kdelibs-3.5.9/./kdecore/kapplication.cpp:550
#13 0x00007f55d973f20e in QApplication::sendEvent (receiver=0x18e52c0, 
    event=0x1986710) at ../include/qapplication.h:523
#14 0x00007f55d97af351 in QApplication::sendPostedEvents (receiver=0x0, 
    event_type=0) at kernel/qapplication.cpp:3302
#15 0x00007f55d97af449 in QApplication::sendPostedEvents ()
    at kernel/qapplication.cpp:3213
#16 0x00007f55d9753054 in QEventLoop::processEvents (this=0x67c4f0, flags=4)
    at kernel/qeventloop_x11.cpp:147
#17 0x00007f55d97c85bf in QEventLoop::enterLoop (this=0x67c4f0)
    at kernel/qeventloop.cpp:201
#18 0x00007f55d97c82ab in QEventLoop::exec (this=0x67c4f0)
    at kernel/qeventloop.cpp:148
#19 0x00007f55d97afe00 in QApplication::exec (this=0x7fffe3df3390)
    at kernel/qapplication.cpp:2761
#20 0x000000000040326f in main (argc=5, argv=0x7fffe3df3638)
    at /build/buildd/digikam-0.9.3/./digikam/digikam/main.cpp:332

Comment 2 caulier.gilles 2008-08-26 09:13:40 UTC

Nathan,

Sound like a broken package installed. The backtrace do not give more informations to hack.

Install last stable digiKam 0.9.4, and try again.

Gilles Caulier

Comment 3 Andi Clemens 2008-10-14 21:33:44 UTC

Nathan,

any news here? Does it work for you now?

Comment 4 Andi Clemens 2008-12-01 22:34:30 UTC

Ping :-)

Comment 5 Andi Clemens 2008-12-01 22:58:56 UTC

forwarding from Nathan:

> 0.9.4 installed during the upgrade to Kubuntu 8.10.  No problems since.

Please post replies directly in the bugreport the next time.
I will close this bug now, if you experience the problem again, you can come back and reopen the bug.

Andi