Bug 195373 - Crash while closing after loading folder with large images
Summary: Crash while closing after loading folder with large images
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Showfoto-Directory (show other bugs)
Version: 0.10.0
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-05 21:29 UTC by Mihaela
Modified: 2022-02-05 05:33 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In: 1.3.0
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mihaela 2009-06-05 21:29:07 UTC
Version:           0.10 (using KDE 4.2.2)
OS:                Linux
Installed from:    Ubuntu Packages

I used to have Digikam on ubuntu 8.10, I think it was 0.94 so I had the database "3" of my photos. I upgraded to ubuntu 9.04 and installed digikam with showFoto. 

Digikam opened up great, recognized my old files, captions etc. Closing went without problems.

Then I opened showFoto and chose to open a folder with lots of images, some of them very large. After the first 2 images appeared I closed showFoto, while processor was running 100%. 

Here are backtraces of 2 different folders I tried to open. 



Application: showFoto (showfoto), signal SIGSEGV
pthread_cond_wait@@GLIBC_2.3.2 ()
    at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:261
	in ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S
Current language:  auto; currently asm
[Current thread is 0 (LWP 13985)]

Thread 2 (Thread 0x7f52df3b1950 (LWP 13987)):
[KCrash Handler]
#5  QFactoryLoader::keys (this=0x0) at plugin/qfactoryloader_p.h:69
#6  0x00007f52ef248c85 in createWriteHandlerHelper (device=0x7f52c00d6670, format=@0x7f52c00de830) at image/qimagewriter.cpp:135
#7  0x00007f52ef24abf8 in QImageWriter::canWrite (this=0x7f52df3b0790) at image/qimagewriter.cpp:537
#8  0x00007f52ef24acc3 in QImageWriter::write (this=0x7f52df3b0630, image=@0x0) at image/qimagewriter.cpp:565
#9  0x00007f52ef2349e6 in QImage::save (this=0x7f52df3b09d0, fileName=@0x7f52df3b0b00, format=<value optimized out>, quality=0) at image/qimage.cpp:4659
#10 0x00007f52f1bc2caf in Digikam::ThumbnailCreator::load (this=0x15883e0, path=@0x2699c58) at /build/buildd/digikam-0.10.0/libs/threadimageio/thumbnailcreator.cpp:252
#11 0x00007f52f1bc86d4 in Digikam::ThumbnailLoadingTask::execute (this=0x2699c40) at /build/buildd/digikam-0.10.0/libs/threadimageio/thumbnailtask.cpp:135
#12 0x00007f52f1baa636 in Digikam::LoadSaveThread::run (this=0x15ca180) at /build/buildd/digikam-0.10.0/libs/threadimageio/loadsavethread.cpp:134
#13 0x00007f52ee4ff952 in QThreadPrivate::start (arg=0x15ca180) at thread/qthread_unix.cpp:189
#14 0x00007f52ebb343ba in start_thread (arg=<value optimized out>) at pthread_create.c:297
#15 0x00007f52eda5cfcd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#16 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f52f210f750 (LWP 13985)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:261
#1  0x00007f52ee500939 in QWaitCondition::wait (this=0x151bc90, mutex=0x151bc70, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:87
#2  0x00007f52ee4ffafc in QThread::wait (this=<value optimized out>, time=18446744073709551615) at thread/qthread_unix.cpp:485
#3  0x00007f52f1baad61 in ~LoadSaveThread (this=0x15ca180) at /build/buildd/digikam-0.10.0/libs/threadimageio/loadsavethread.cpp:80
#4  0x00007f52f1bad618 in ~ManagedLoadSaveThread (this=0x15ca180) at /build/buildd/digikam-0.10.0/libs/threadimageio/managedloadsavethread.cpp:69
#5  0x00007f52f1bc4fc4 in ~ThumbnailLoadThread (this=0x15ca180) at /build/buildd/digikam-0.10.0/libs/threadimageio/thumbnailloadthread.cpp:115
#6  0x00007f52ed9ad6ed in *__GI_exit (status=0) at exit.c:75
#7  0x00007f52ed9955ad in __libc_start_main (main=0x4304f0 <main>, argc=5, ubp_av=0x7ffffa156ae8, init=0x43d480 <__libc_csu_init>, fini=<value optimized out>, rtld_fini=<value optimized out>, 
    stack_end=0x7ffffa156ad8) at libc-start.c:252
#8  0x0000000000411639 in _start () at ../sysdeps/x86_64/elf/start.S:113
Current language:  auto; currently c
261	in ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S
Current language:  auto; currently asm



The second one: 


Application: showFoto (showfoto), signal SIGSEGV
pthread_cond_wait@@GLIBC_2.3.2 ()
    at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:261
	in ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S
Current language:  auto; currently asm
[Current thread is 0 (LWP 14049)]

Thread 2 (Thread 0x7f254729f950 (LWP 14051)):
[KCrash Handler]
#5  Digikam::ThumbnailCreator::loadWithDImg (this=0x2271ea0, path=@0x3399f48) at /usr/include/qt4/QtCore/qatomic_x86_64.h:121
#6  0x00007f2559ab0fe6 in Digikam::ThumbnailCreator::load (this=0x2271ea0, path=@0x3399f48) at /build/buildd/digikam-0.10.0/libs/threadimageio/thumbnailcreator.cpp:195
#7  0x00007f2559ab66d4 in Digikam::ThumbnailLoadingTask::execute (this=0x3399f30) at /build/buildd/digikam-0.10.0/libs/threadimageio/thumbnailtask.cpp:135
#8  0x00007f2559a98636 in Digikam::LoadSaveThread::run (this=0x22719e0) at /build/buildd/digikam-0.10.0/libs/threadimageio/loadsavethread.cpp:134
#9  0x00007f25563ed952 in QThreadPrivate::start (arg=0x22719e0) at thread/qthread_unix.cpp:189
#10 0x00007f2553a223ba in start_thread (arg=<value optimized out>) at pthread_create.c:297
#11 0x00007f255594afcd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#12 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f2559ffd750 (LWP 14049)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:261
#1  0x00007f25563ee939 in QWaitCondition::wait (this=0x2271ae0, mutex=0x2271ac0, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:87
#2  0x00007f25563edafc in QThread::wait (this=<value optimized out>, time=18446744073709551615) at thread/qthread_unix.cpp:485
#3  0x00007f2559a98d61 in ~LoadSaveThread (this=0x22719e0) at /build/buildd/digikam-0.10.0/libs/threadimageio/loadsavethread.cpp:80
#4  0x00007f2559a9b618 in ~ManagedLoadSaveThread (this=0x22719e0) at /build/buildd/digikam-0.10.0/libs/threadimageio/managedloadsavethread.cpp:69
#5  0x00007f2559ab2fc4 in ~ThumbnailLoadThread (this=0x22719e0) at /build/buildd/digikam-0.10.0/libs/threadimageio/thumbnailloadthread.cpp:115
#6  0x00007f255589b6ed in *__GI_exit (status=0) at exit.c:75
#7  0x00007f25558835ad in __libc_start_main (main=0x4304f0 <main>, argc=5, ubp_av=0x7fff620449d8, init=0x43d480 <__libc_csu_init>, fini=<value optimized out>, rtld_fini=<value optimized out>, 
    stack_end=0x7fff620449c8) at libc-start.c:252
#8  0x0000000000411639 in _start () at ../sysdeps/x86_64/elf/start.S:113
Current language:  auto; currently c
261	in ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S
Current language:  auto; currently asm
Comment 1 caulier.gilles 2009-06-05 21:41:11 UTC
What's your images size ?

How many memory you have on your computer ?

Which image format you use ?

Which program have generated these images ?

Gilles Caulier
Comment 2 Mihaela 2009-06-05 22:24:21 UTC
Images sizes: 
first case: first image 7.3MB, second image 5,6 MB
second case: first image 0.5KB, I don't know which went second, probably small one

I have 4GB of RAM

Jpg for large ones and png for the small one

The large ones are photos from a stock photo site, probably edited in Photoshop or similar, the png probably edited in GIMP.
Comment 3 Dario Andres 2009-06-06 14:46:12 UTC
BT at bug 167725 could be related but it is a bit old
Comment 4 Kai Wb. 2009-06-15 20:47:25 UTC
It seems like this issue can also be invoked by simply trying to open a large JPEG image. Please see http://bugs.debian.org/533219 for the full description and the backtrace.

The Debian bug #533219 has been forwarded to this report.

Kind regards,
Kai Wasserbäch
Comment 5 Andi Clemens 2009-06-26 09:50:00 UTC
Hmm works fine here, showFoto 1.0.0 and exiv2-0.18
Comment 6 caulier.gilles 2009-12-25 20:21:58 UTC
digiKam 1.0.0 is out since few days...

http://www.digikam.org/drupal/node/491

Please try with this version coming with more than 400 bug-fixes.

Thanks in advance

Gilles Caulier
Comment 7 caulier.gilles 2010-04-04 10:42:40 UTC
digiKam and Kipi-plugins 1.2.0 are out. Please check if crash is still valid there.

Thanks in advance

Gilles Caulier
Comment 8 Mihaela 2010-04-07 03:08:20 UTC
I tried the 1.2.0 versions of Digikam and Showfoto, the kipi-plugins are 0.7.0-1ubuntu2. 

I tried to open a folder with a lot of large photos and close it before all the thumbnails show up, there is no crash. 

Is there anything else I need to do to test this?
Comment 9 caulier.gilles 2010-04-07 08:43:48 UTC
No, nothing more to do. If you is not able to reproduce the crash, it's fine.

I close this file now. Re-open it if necessary.

Thanks for the feedback.

Gilles Caulier