[Bug 218435] New: digiKam segfaults when running 'Rebuild All Thumbnails' after 200 photos

classic Classic list List threaded Threaded
14 messages Options
Reply | Threaded
Open this post in threaded view
|

[Bug 218435] New: digiKam segfaults when running 'Rebuild All Thumbnails' after 200 photos

Bugzilla from caffeinated_eric@hotmail.com
https://bugs.kde.org/show_bug.cgi?id=218435

           Summary: digiKam segfaults when running 'Rebuild All
                    Thumbnails' after 200 photos
           Product: digikam
           Version: unspecified
          Platform: Unlisted Binaries
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: crash
          Priority: NOR
         Component: general
        AssignedTo: [hidden email]
        ReportedBy: [hidden email]


Application that crashed: digikam
Version of the application: rc..-rc
KDE Version: 4.3.4 (KDE 4.3.4)
Qt Version: 4.5.2
Operating System: Linux 2.6.31-17-generic i686
Distribution: Ubuntu 9.10

What I was doing when the application crashed:
I can reproduce a segfault in digiKam 1.0.0 RC by choosing the Tools -> Rebuild
All Thumbails option.  The tool gets through about 200 images, then segfaults.

Running on Ubuntu 9.10

 -- Backtrace:
Application: digiKam (digikam), signal: Segmentation fault
[Current thread is 1 (Thread 0xb77e8700 (LWP 21339))]

Thread 16 (Thread 0xb6225b70 (LWP 21340)):
#0  0x0057d422 in __kernel_vsyscall ()
#1  0x007d5e15 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib/tls/i686/cmov/libpthread.so.0
#2  0x0220578d in pthread_cond_wait () from /lib/tls/i686/cmov/libc.so.6
#3  0x03b40e67 in QWaitConditionPrivate::wait (this=0x91e85d0, mutex=0x91e85cc,
time=4294967295) at thread/qwaitcondition_unix.cpp:87
#4  QWaitCondition::wait (this=0x91e85d0, mutex=0x91e85cc, time=4294967295) at
thread/qwaitcondition_unix.cpp:159
#5  0x083184f9 in Digikam::ScanController::run (this=0x91ec5b0) at
/build/buildd/digikam-1.0.0~rc/digikam/scancontroller.cpp:499
#6  0x03b3fe32 in QThreadPrivate::start (arg=0x91ec5b0) at
thread/qthread_unix.cpp:188
#7  0x007d180e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#8  0x021f87ee in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 15 (Thread 0xb598cb70 (LWP 21342)):
#0  0x078a7e06 in clock_gettime () from /lib/tls/i686/cmov/librt.so.1
#1  0x03c5cbf3 in QTimerInfoList::getTime (this=0xb5036714, t=...) at
kernel/qeventdispatcher_unix.cpp:339
#2  0x03c5cde1 in QTimerInfoList::updateCurrentTime (this=0xb5036714) at
kernel/qeventdispatcher_unix.cpp:297
#3  0x03c5d88c in QTimerInfoList::timerWait (this=0xb5036714, tm=...) at
kernel/qeventdispatcher_unix.cpp:420
#4  0x03c5b210 in timerSourcePrepare (source=0xb50366e0, timeout=0xb598c11c) at
kernel/qeventdispatcher_glib.cpp:141
#5  0x06d78f90 in g_main_context_prepare () from /lib/libglib-2.0.so.0
#6  0x06d79351 in ?? () from /lib/libglib-2.0.so.0
#7  0x06d79863 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#8  0x03c5b067 in QEventDispatcherGlib::processEvents (this=0x934cb30,
flags=...) at kernel/qeventdispatcher_glib.cpp:329
#9  0x03c2ec79 in QEventLoop::processEvents (this=0xb598c2e4, flags=) at
kernel/qeventloop.cpp:149
#10 0x03c2f0ca in QEventLoop::exec (this=0xb598c2e4, flags=...) at
kernel/qeventloop.cpp:201
#11 0x03b3cb73 in QThread::exec (this=0x934a688) at thread/qthread.cpp:487
#12 0x003b12dd in Digikam::ImageFilterModelWorker::Thread::run() () from
/usr/lib/libdigikamdatabase.so.1
#13 0x03b3fe32 in QThreadPrivate::start (arg=0x934a688) at
thread/qthread_unix.cpp:188
#14 0x007d180e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#15 0x021f87ee in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 14 (Thread 0xb4dffb70 (LWP 21343)):
#0  0x078a7e06 in clock_gettime () from /lib/tls/i686/cmov/librt.so.1
#1  0x03c5cbf3 in QTimerInfoList::getTime (this=0xb500f1c4, t=...) at
kernel/qeventdispatcher_unix.cpp:339
#2  0x03c5cde1 in QTimerInfoList::updateCurrentTime (this=0xb500f1c4) at
kernel/qeventdispatcher_unix.cpp:297
#3  0x03c5d88c in QTimerInfoList::timerWait (this=0xb500f1c4, tm=...) at
kernel/qeventdispatcher_unix.cpp:420
#4  0x03c5b210 in timerSourcePrepare (source=0xb500f190, timeout=0xb4dff11c) at
kernel/qeventdispatcher_glib.cpp:141
#5  0x06d78f90 in g_main_context_prepare () from /lib/libglib-2.0.so.0
#6  0x06d79351 in ?? () from /lib/libglib-2.0.so.0
#7  0x06d79863 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#8  0x03c5b067 in QEventDispatcherGlib::processEvents (this=0xb50070b8,
flags=...) at kernel/qeventdispatcher_glib.cpp:329
#9  0x03c2ec79 in QEventLoop::processEvents (this=0xb4dff2e4, flags=) at
kernel/qeventloop.cpp:149
#10 0x03c2f0ca in QEventLoop::exec (this=0xb4dff2e4, flags=...) at
kernel/qeventloop.cpp:201
#11 0x03b3cb73 in QThread::exec (this=0x934c6e0) at thread/qthread.cpp:487
#12 0x003b12dd in Digikam::ImageFilterModelWorker::Thread::run() () from
/usr/lib/libdigikamdatabase.so.1
#13 0x03b3fe32 in QThreadPrivate::start (arg=0x934c6e0) at
thread/qthread_unix.cpp:188
#14 0x007d180e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#15 0x021f87ee in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 13 (Thread 0xb45feb70 (LWP 21344)):
#0  0x0057d422 in __kernel_vsyscall ()
#1  0x007d5e15 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib/tls/i686/cmov/libpthread.so.0
#2  0x0220578d in pthread_cond_wait () from /lib/tls/i686/cmov/libc.so.6
#3  0x03b40e67 in QWaitConditionPrivate::wait (this=0x942d7d0, mutex=0x942d7cc,
time=4294967295) at thread/qwaitcondition_unix.cpp:87
#4  QWaitCondition::wait (this=0x942d7d0, mutex=0x942d7cc, time=4294967295) at
thread/qwaitcondition_unix.cpp:159
#5  0x0422e28a in Digikam::LoadSaveThread::run (this=0x942d7c0) at
/build/buildd/digikam-1.0.0~rc/libs/threadimageio/loadsavethread.cpp:131
#6  0x03b3fe32 in QThreadPrivate::start (arg=0x942d7c0) at
thread/qthread_unix.cpp:188
#7  0x007d180e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#8  0x021f87ee in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 12 (Thread 0xb3dfdb70 (LWP 21345)):
#0  0x007d3d4b in pthread_mutex_lock () from /lib/tls/i686/cmov/libpthread.so.0
#1  0x02205956 in pthread_mutex_lock () from /lib/tls/i686/cmov/libc.so.6
#2  0x06d78d0c in g_main_context_check () from /lib/libglib-2.0.so.0
#3  0x06d7947c in ?? () from /lib/libglib-2.0.so.0
#4  0x06d79863 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#5  0x03c5b067 in QEventDispatcherGlib::processEvents (this=0x944bb50,
flags=...) at kernel/qeventdispatcher_glib.cpp:329
#6  0x03c2ec79 in QEventLoop::processEvents (this=0xb3dfd304, flags=) at
kernel/qeventloop.cpp:149
#7  0x03c2f0ca in QEventLoop::exec (this=0xb3dfd304, flags=...) at
kernel/qeventloop.cpp:201
#8  0x03b3cb73 in QThread::exec (this=0x944a7d8) at thread/qthread.cpp:487
#9  0x03b3fe32 in QThreadPrivate::start (arg=0x944a7d8) at
thread/qthread_unix.cpp:188
#10 0x007d180e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#11 0x021f87ee in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 11 (Thread 0xb35fcb70 (LWP 21346)):
#0  0x0057d422 in __kernel_vsyscall ()
#1  0x021eaba6 in poll () from /lib/tls/i686/cmov/libc.so.6
#2  0x06d8654b in g_poll () from /lib/libglib-2.0.so.0
#3  0x06d7956b in ?? () from /lib/libglib-2.0.so.0
#4  0x06d79863 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#5  0x03c5b067 in QEventDispatcherGlib::processEvents (this=0x9432708,
flags=...) at kernel/qeventdispatcher_glib.cpp:329
#6  0x03c2ec79 in QEventLoop::processEvents (this=0xb35fc304, flags=) at
kernel/qeventloop.cpp:149
#7  0x03c2f0ca in QEventLoop::exec (this=0xb35fc304, flags=...) at
kernel/qeventloop.cpp:201
#8  0x03b3cb73 in QThread::exec (this=0x94317e8) at thread/qthread.cpp:487
#9  0x03b3fe32 in QThreadPrivate::start (arg=0x94317e8) at
thread/qthread_unix.cpp:188
#10 0x007d180e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#11 0x021f87ee in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 10 (Thread 0xb2dfbb70 (LWP 21347)):
#0  0x0057d422 in __kernel_vsyscall ()
#1  0x007d5e15 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib/tls/i686/cmov/libpthread.so.0
#2  0x0220578d in pthread_cond_wait () from /lib/tls/i686/cmov/libc.so.6
#3  0x03b40e67 in QWaitConditionPrivate::wait (this=0x9446870, mutex=0x944686c,
time=4294967295) at thread/qwaitcondition_unix.cpp:87
#4  QWaitCondition::wait (this=0x9446870, mutex=0x944686c, time=4294967295) at
thread/qwaitcondition_unix.cpp:159
#5  0x0422e28a in Digikam::LoadSaveThread::run (this=0x9446860) at
/build/buildd/digikam-1.0.0~rc/libs/threadimageio/loadsavethread.cpp:131
#6  0x03b3fe32 in QThreadPrivate::start (arg=0x9446860) at
thread/qthread_unix.cpp:188
#7  0x007d180e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#8  0x021f87ee in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 9 (Thread 0xb119db70 (LWP 21348)):
#0  0x0057d422 in __kernel_vsyscall ()
#1  0x007d6142 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib/tls/i686/cmov/libpthread.so.0
#2  0x022057e4 in pthread_cond_timedwait () from /lib/tls/i686/cmov/libc.so.6
#3  0x031bebab in ?? () from /usr/lib/libxine.so.1
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

Thread 8 (Thread 0xb0591b70 (LWP 21349)):
#0  0x0057d422 in __kernel_vsyscall ()
#1  0x021f1981 in select () from /lib/tls/i686/cmov/libc.so.6
#2  0x031e7cb0 in xine_usec_sleep () from /usr/lib/libxine.so.1
#3  0x00000000 in ?? ()

Thread 7 (Thread 0xafd90b70 (LWP 21350)):
#0  0x0057d422 in __kernel_vsyscall ()
#1  0x02205ae3 in ?? () from /lib/tls/i686/cmov/libc.so.6
#2  0x0219cf07 in ?? () from /lib/tls/i686/cmov/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 6 (Thread 0xaf58fb70 (LWP 21351)):
#0  0x06cb8c54 in pa_mutex_lock () from /usr/lib/libpulsecommon-0.9.19.so
#1  0x085c6ccc in ?? () from /usr/lib/libpulse.so.0
#2  0x085b3e09 in pa_mainloop_poll () from /usr/lib/libpulse.so.0
#3  0x085b5c23 in pa_mainloop_iterate () from /usr/lib/libpulse.so.0
#4  0x085b5cf4 in pa_mainloop_run () from /usr/lib/libpulse.so.0
#5  0x085c6bc3 in ?? () from /usr/lib/libpulse.so.0
#6  0x06cb9ac2 in ?? () from /usr/lib/libpulsecommon-0.9.19.so
#7  0x007d180e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#8  0x021f87ee in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 5 (Thread 0xaad8db70 (LWP 21352)):
#0  0x0057d422 in __kernel_vsyscall ()
#1  0x007d5e15 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib/tls/i686/cmov/libpthread.so.0
#2  0x0220578d in pthread_cond_wait () from /lib/tls/i686/cmov/libc.so.6
#3  0x031cf78a in ?? () from /usr/lib/libxine.so.1
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

Thread 4 (Thread 0xa8ce2b70 (LWP 21362)):
#0  0x0057d422 in __kernel_vsyscall ()
#1  0x007d5e15 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib/tls/i686/cmov/libpthread.so.0
#2  0x0220578d in pthread_cond_wait () from /lib/tls/i686/cmov/libc.so.6
#3  0x03b40e67 in QWaitConditionPrivate::wait (this=0x9e7da38, mutex=0x9e7da34,
time=4294967295) at thread/qwaitcondition_unix.cpp:87
#4  QWaitCondition::wait (this=0x9e7da38, mutex=0x9e7da34, time=4294967295) at
thread/qwaitcondition_unix.cpp:159
#5  0x0422e28a in Digikam::LoadSaveThread::run (this=0x9e7da28) at
/build/buildd/digikam-1.0.0~rc/libs/threadimageio/loadsavethread.cpp:131
#6  0x03b3fe32 in QThreadPrivate::start (arg=0x9e7da28) at
thread/qthread_unix.cpp:188
#7  0x007d180e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#8  0x021f87ee in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 3 (Thread 0xa82ffb70 (LWP 21370)):
#0  0x0057d422 in __kernel_vsyscall ()
#1  0x007d5e15 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib/tls/i686/cmov/libpthread.so.0
#2  0x0220578d in pthread_cond_wait () from /lib/tls/i686/cmov/libc.so.6
#3  0x03b40e67 in QWaitConditionPrivate::wait (this=0xa3fe740, mutex=0xa3fe73c,
time=4294967295) at thread/qwaitcondition_unix.cpp:87
#4  QWaitCondition::wait (this=0xa3fe740, mutex=0xa3fe73c, time=4294967295) at
thread/qwaitcondition_unix.cpp:159
#5  0x0422e28a in Digikam::LoadSaveThread::run (this=0xa3fe730) at
/build/buildd/digikam-1.0.0~rc/libs/threadimageio/loadsavethread.cpp:131
#6  0x03b3fe32 in QThreadPrivate::start (arg=0xa3fe730) at
thread/qthread_unix.cpp:188
#7  0x007d180e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#8  0x021f87ee in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 2 (Thread 0xa37ffb70 (LWP 21388)):
[KCrash Handler]
#6  0x02199bf2 in ?? () from /lib/tls/i686/cmov/libc.so.6
#7  0x0219b868 in malloc () from /lib/tls/i686/cmov/libc.so.6
#8  0x00dcbbb7 in operator new(unsigned int) () from /usr/lib/libstdc++.so.6
#9  0x00dcbced in operator new[](unsigned int) () from /usr/lib/libstdc++.so.6
#10 0x0415022d in Digikam::DImg::allocateData (this=0xa37fee0c) at
/build/buildd/digikam-1.0.0~rc/libs/dimg/dimg.cpp:298
#11 0x041563ca in DImg (this=0xa37fee0c, image=..., w=73, h=128) at
/build/buildd/digikam-1.0.0~rc/libs/dimg/dimg.cpp:127
#12 0x041623e7 in Digikam::DImg::smoothScale (this=0xbf23544, dw=73, dh=128,
aspectRatioMode=Qt::IgnoreAspectRatio) at
/build/buildd/digikam-1.0.0~rc/libs/dimg/dimgscale.cpp:132
#13 0x04246dd8 in Digikam::PreviewLoadingTask::execute (this=0xbf23450) at
/build/buildd/digikam-1.0.0~rc/libs/threadimageio/previewtask.cpp:277
#14 0x0422e25a in Digikam::LoadSaveThread::run (this=0xa607940) at
/build/buildd/digikam-1.0.0~rc/libs/threadimageio/loadsavethread.cpp:134
#15 0x03b3fe32 in QThreadPrivate::start (arg=0xa607940) at
thread/qthread_unix.cpp:188
#16 0x007d180e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#17 0x021f87ee in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 1 (Thread 0xb77e8700 (LWP 21339)):
#0  0x0057d422 in __kernel_vsyscall ()
#1  0x007d5e15 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib/tls/i686/cmov/libpthread.so.0
#2  0x0220578d in pthread_cond_wait () from /lib/tls/i686/cmov/libc.so.6
#3  0x03b3f4d2 in QMutexPrivate::wait (this=0x904b198, timeout=-1) at
thread/qmutex_unix.cpp:80
#4  0x03b3aba2 in QMutex::lock (this=0x904acdc) at thread/qmutex.cpp:207
#5  0x03c464e1 in QMutexLocker::relock (sender=0x99941f0, from_signal_index=0,
to_signal_index=1, argv=0xbfb23f58) at
../../include/QtCore/../../src/corelib/thread/qmutex.h:120
#6  QMutexLocker (sender=0x99941f0, from_signal_index=0, to_signal_index=1,
argv=0xbfb23f58) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:102
#7  QMetaObject::activate (sender=0x99941f0, from_signal_index=0,
to_signal_index=1, argv=0xbfb23f58) at kernel/qobject.cpp:3052
#8  0x03c466d8 in QMetaObject::activate (sender=0x99941f0, m=0x84ba9e0,
from_local_signal_index=0, to_local_signal_index=1, argv=0xbfb23f58) at
kernel/qobject.cpp:3207
#9  0x03c4676b in QObject::destroyed (this=0x99941f0, _t1=0x99941f0) at
.moc/release-shared/moc_qobject.cpp:143
#10 0x03c47536 in ~QObject (this=0x99941f0, __in_chrg=<value optimized out>) at
kernel/qobject.cpp:757
#11 0x03177fd0 in ?? () from /usr/lib/qt4/plugins/phonon_backend/phonon_xine.so
#12 0x0012ccec in Phonon::MediaNodePrivate::deleteBackendObject
(this=0x9994138) at ../3rdparty/phonon/phonon/medianode.cpp:81
#13 0x0013c147 in ~FactoryPrivate (this=0x950cfe0, __in_chrg=<value optimized
out>) at ../3rdparty/phonon/phonon/factory.cpp:193
#14 0x0013ada5 in destroy () at ../3rdparty/phonon/phonon/factory.cpp:84
#15 0x0013847b in ~CleanUpGlobalStatic (this=0x15d3f0, __in_chrg=<value
optimized out>) at ../3rdparty/phonon/phonon/globalstatic_p.h:55
#16 0x0215b05f in ?? () from /lib/tls/i686/cmov/libc.so.6
#17 0x0215b0cf in exit () from /lib/tls/i686/cmov/libc.so.6
#18 0x07f17610 in ?? () from /usr/lib/libgdk-x11-2.0.so.0
#19 0x02a88afa in KApplication::xioErrhandler (this=0xbfb245c8, dpy=0x908d3f8)
at ../../kdeui/kernel/kapplication.cpp:408
#20 0x02a88b36 in kde_xio_errhandler (dpy=0x908d3f8) at
../../kdeui/kernel/kapplication.cpp:125
#21 0x022a92e6 in _XIOError () from /usr/lib/libX11.so.6
#22 0x022b0f8a in ?? () from /usr/lib/libX11.so.6
#23 0x022b18c6 in _XEventsQueued () from /usr/lib/libX11.so.6
#24 0x0229a5ff in XEventsQueued () from /usr/lib/libX11.so.6
#25 0x01702db5 in x11EventSourceCheck (s=0x9073af8) at
kernel/qguieventdispatcher_glib.cpp:87
#26 0x06d78cd1 in g_main_context_check () from /lib/libglib-2.0.so.0
#27 0x06d7947c in ?? () from /lib/libglib-2.0.so.0
#28 0x06d79863 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#29 0x03c5b02c in QEventDispatcherGlib::processEvents (this=0x904ae80,
flags=...) at kernel/qeventdispatcher_glib.cpp:327
#30 0x01702be5 in QGuiEventDispatcherGlib::processEvents (this=0x904ae80,
flags=...) at kernel/qguieventdispatcher_glib.cpp:202
#31 0x03c2ec79 in QEventLoop::processEvents (this=0xbfb24514, flags=) at
kernel/qeventloop.cpp:149
#32 0x03c2f0ca in QEventLoop::exec (this=0xbfb24514, flags=...) at
kernel/qeventloop.cpp:201
#33 0x03c3153f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#34 0x01661dd7 in QApplication::exec () at kernel/qapplication.cpp:3525
#35 0x083bb51b in main (argc=5, argv=0xbfb24a34) at
/build/buildd/digikam-1.0.0~rc/digikam/main.cpp:195

Reported using DrKonqi

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

[Bug 218435] digiKam segfaults when running 'Rebuild All Thumbnails' after 200 photos

Gilles Caulier-4
https://bugs.kde.org/show_bug.cgi?id=218435


Gilles Caulier <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|general                     |Xine backend
            Product|digikam                     |Phonon




--- Comment #1 from Gilles Caulier <caulier gilles gmail com>  2009-12-12 21:55:11 ---
Crash appears in Phonon/Xine backend when video thumbnails are generated. Check
your system...

Gilles Caulier

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

[Bug 218435] digiKam segfaults when running 'Rebuild All Thumbnails' after 200 photos

Gilles Caulier-4
In reply to this post by Bugzilla from caffeinated_eric@hotmail.com
https://bugs.kde.org/show_bug.cgi?id=218435


Gilles Caulier <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]
         AssignedTo|[hidden email]       |[hidden email]




--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

[Bug 218435] digiKam segfaults when running 'Rebuild All Thumbnails' after 200 photos

Gilles Caulier-4
In reply to this post by Bugzilla from caffeinated_eric@hotmail.com
https://bugs.kde.org/show_bug.cgi?id=218435


Gilles Caulier <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|[hidden email]               |[hidden email]




--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

[Bug 218435] digiKam segfaults when running 'Rebuild All Thumbnails' after 200 photos

Marcel Wiesweg
In reply to this post by Bugzilla from caffeinated_eric@hotmail.com
https://bugs.kde.org/show_bug.cgi?id=218435


Marcel Wiesweg <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]




--- Comment #12 from Marcel Wiesweg <marcel wiesweg gmx de>  2010-01-21 18:12:53 ---
This is not the not-enough-memory-cannot-allocate problem. There must be memory
corruption somewhere. Only running under valgrind could probably help any
further here.
Alternatively, please identify the last image accessed before the crash. Enable
debug messages (run "kdebugdialog" and enable code 50003), then look at the
last lines before the crash. You will certainly see a filename there.
Pass that filename to exiv2 -p a and see if it crashes.

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

[Bug 218435] digiKam segfaults when running 'Rebuild All Thumbnails' after 200 photos

Gilles Caulier-4
In reply to this post by Bugzilla from caffeinated_eric@hotmail.com
https://bugs.kde.org/show_bug.cgi?id=218435





--- Comment #13 from Gilles Caulier <caulier gilles gmail com>  2010-01-25 21:51:55 ---
digiKam 1.1. release will be done in few days. Please check if this entry still
valid.

Thanks in advance

Gilles Caulier

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

[Bug 218435] digiKam segfaults when running 'Rebuild All Thumbnails' after 200 photos

Gilles Caulier-4
In reply to this post by Bugzilla from caffeinated_eric@hotmail.com
https://bugs.kde.org/show_bug.cgi?id=218435





--- Comment #14 from Gilles Caulier <caulier gilles gmail com>  2010-04-04 10:45:32 ---
digiKam and Kipi-plugins 1.2.0 are out. Please check if crash is still valid
there.

Thanks in advance

Gilles Caulier

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

[Bug 218435] digiKam segfaults when running 'Rebuild All Thumbnails' after 200 photos

Bugzilla from caffeinated_eric@hotmail.com
In reply to this post by Bugzilla from caffeinated_eric@hotmail.com
https://bugs.kde.org/show_bug.cgi?id=218435





--- Comment #15 from Eric T. Schaffner <caffeinated_eric hotmail com>  2010-07-03 01:51:03 ---
Greetings Gilles,

The problem still exists with digikam and kipi-plugins 1.3.0 - but only if I
use the SQLLite back end.  If I switch to the MySQL back end, thumbnailing
proceeds normally through all 15,000 raw files.

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

[Bug 218435] digiKam segfaults when running 'Rebuild All Thumbnails' after 200 photos

Gilles Caulier-4
In reply to this post by Bugzilla from caffeinated_eric@hotmail.com
https://bugs.kde.org/show_bug.cgi?id=218435





--- Comment #16 from Gilles Caulier <caulier gilles gmail com>  2010-10-06 13:21:01 ---
Eric,

And trying digiKam 1.4.0 ?

Can you try to run digiKam through valgrind to see where are located all memory
corruption. Look there for details :

http://lxr.kde.org/source/extragear/graphics/digikam/HACKING#235

Gilles Caulier

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

[Bug 218435] digiKam segfaults when running 'Rebuild All Thumbnails' after 200 photos

Gilles Caulier-4
In reply to this post by Bugzilla from caffeinated_eric@hotmail.com
https://bugs.kde.org/show_bug.cgi?id=218435


Gilles Caulier <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Version|1.0.0                       |1.3.0




--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

[Bug 218435] digiKam segfaults when running 'Rebuild All Thumbnails' after 200 photos

Gilles Caulier-4
In reply to this post by Bugzilla from caffeinated_eric@hotmail.com
https://bugs.kde.org/show_bug.cgi?id=218435





--- Comment #17 from Gilles Caulier <caulier gilles gmail com>  2010-11-24 09:07:18 ---
digiKam 1.6.0 is out:

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

Please update and check if this entry still valid.

Thanks in advance

Gilles Caulier

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

[Bug 218435] digiKam segfaults when running 'Rebuild All Thumbnails' after 200 photos

Marcel Wiesweg
In reply to this post by Bugzilla from caffeinated_eric@hotmail.com
https://bugs.kde.org/show_bug.cgi?id=218435


Marcel Wiesweg <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |WAITINGFORINFO




--- Comment #18 from Marcel Wiesweg <marcel wiesweg gmx de>  2011-01-18 14:24:27 ---
This report is now rather old, and mixing completely different traces.

Please reopen when you encounter again with a recent digikam (1.7, 2.0) and
recent dependencies (libexiv2).

It would be alsp useful to watch debugging output on the console (run
kdebugdialog, enable 50003) to see if it's a specific image related to the
crash (filename usually printed on the console).

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

[digikam] [Bug 218435] digiKam segfaults when running 'Rebuild All Thumbnails' after 200 photos

Gilles Caulier-4
In reply to this post by Bugzilla from caffeinated_eric@hotmail.com
https://bugs.kde.org/show_bug.cgi?id=218435

--- Comment #19 from Gilles Caulier <[hidden email]> ---
New digiKam 4.11.0 is available.

https://www.digikam.org/node/740

Can you reproduce the problem with this release ?

Gilles Caulier

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

[digikam] [Bug 218435] digiKam segfaults when running 'Rebuild All Thumbnails' after 200 photos

bugzilla_noreply
In reply to this post by Bugzilla from caffeinated_eric@hotmail.com
https://bugs.kde.org/show_bug.cgi?id=218435

[hidden email] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Version Fixed In|                            |5.1.0
         Resolution|WAITINGFORINFO              |FIXED

--- Comment #20 from [hidden email] ---
With digiKam 5.0.0, this problem is not reproducible.
I close this file now. Don't hesitate to re-open if necessary.
Gilles Caulier

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel