https://bugs.kde.org/show_bug.cgi?id=320253
Bug ID: 320253 Summary: crash on thumb generation, large tiff's Classification: Unclassified Product: digikam Version: 3.1.0 Platform: Debian testing OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: [hidden email] Reporter: [hidden email] Application: digikam (3.1.0) KDE Platform Version: 4.8.4 (4.8.4) Qt Version: 4.8.2 Operating System: Linux 2.6.32-5-686 i686 Distribution (Platform): Debian testing -- Information about the crash: - What I was doing when the application crashed: digikam was generating thumbs, possibly crashing on large tiff's The crash can be reproduced every time. -- Backtrace: Application: digiKam (digikam), signal: Aborted Using host libthread_db library "/lib/i386-linux-gnu/i686/cmov/libthread_db.so.1". [Current thread is 1 (Thread 0xae9568c0 (LWP 15920))] Thread 6 (Thread 0xac620b70 (LWP 15921)): #0 0xb76f9424 in __kernel_vsyscall () #1 0xb34bb20a in __pthread_cond_wait (cond=0x9c6b030, mutex=0x9c6b018) at pthread_cond_wait.c:153 #2 0xb4a3287d in __pthread_cond_wait (cond=0x9c6b030, mutex=0x9c6b018) at forward.c:139 #3 0xb4cd1470 in wait (time=4294967295, this=0x9c6b018) at thread/qwaitcondition_unix.cpp:86 #4 QWaitCondition::wait (this=0x9c6af84, mutex=0x9c6af80, time=4294967295) at thread/qwaitcondition_unix.cpp:158 #5 0x08211686 in ?? () #6 0xb4cd0f00 in QThreadPrivate::start (arg=0x9c52478) at thread/qthread_unix.cpp:307 #7 0xb34b6c39 in start_thread (arg=0xac620b70) at pthread_create.c:304 #8 0xb4a2578e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130 Thread 5 (Thread 0xabe1fb70 (LWP 15922)): #0 0xb2ffce11 in *__GI_clock_gettime (clock_id=1, tp=0xabe1ee58) at ../sysdeps/unix/clock_gettime.c:116 #1 0xb4d2fa35 in do_gettime (frac=0xabe1ee50, sec=0xabe1ee48) at tools/qelapsedtimer_unix.cpp:123 #2 qt_gettime () at tools/qelapsedtimer_unix.cpp:140 #3 0xb4e1521e in QTimerInfoList::updateCurrentTime (this=0x9ca2134) at kernel/qeventdispatcher_unix.cpp:343 #4 0x09c89af8 in ?? () Backtrace stopped: previous frame inner to this frame (corrupt stack?) Thread 4 (Thread 0xab61eb70 (LWP 15926)): #0 0xb76f9424 in __kernel_vsyscall () #1 0xb34bb20a in __pthread_cond_wait (cond=0x9f25160, mutex=0x9f25148) at pthread_cond_wait.c:153 #2 0xb4a3287d in __pthread_cond_wait (cond=0x9f25160, mutex=0x9f25148) at forward.c:139 #3 0xb4cd1470 in wait (time=4294967295, this=0x9f25148) at thread/qwaitcondition_unix.cpp:86 #4 QWaitCondition::wait (this=0x9cca378, mutex=0x9cca374, time=4294967295) at thread/qwaitcondition_unix.cpp:158 #5 0xb69dc8cc in ?? () from /usr/lib/libdigikamcore.so.3 #6 0xb4cd0f00 in QThreadPrivate::start (arg=0x9cca368) at thread/qthread_unix.cpp:307 #7 0xb34b6c39 in start_thread (arg=0xab61eb70) at pthread_create.c:304 #8 0xb4a2578e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130 Thread 3 (Thread 0x96513b70 (LWP 16036)): [KCrash Handler] #6 0xb76f9424 in __kernel_vsyscall () #7 0xb497a941 in *__GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #8 0xb497dd72 in *__GI_abort () at abort.c:92 #9 0xb4b4728d in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/i386-linux-gnu/libstdc++.so.6 #10 0xb4b44ef3 in ?? () from /usr/lib/i386-linux-gnu/libstdc++.so.6 #11 0xb4b44f2f in std::terminate() () from /usr/lib/i386-linux-gnu/libstdc++.so.6 #12 0xb4b45225 in __cxa_rethrow () from /usr/lib/i386-linux-gnu/libstdc++.so.6 #13 0xb4cc3ae2 in QThreadPoolThread::run (this=0xa92623c0) at concurrent/qthreadpool.cpp:114 #14 0xb4cd0f00 in QThreadPrivate::start (arg=0xa92623c0) at thread/qthread_unix.cpp:307 #15 0xb34b6c39 in start_thread (arg=0x96513b70) at pthread_create.c:304 #16 0xb4a2578e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130 Thread 2 (Thread 0x94effb70 (LWP 16039)): #0 0xb3904d02 in sys_futex0 (val=12, op=<optimized out>, addr=0x9841bbd4) at ../../../src/libgomp/config/linux/x86/futex.h:90 #1 futex_wait (val=12, addr=0x9841bbd4) at ../../../src/libgomp/config/linux/x86/futex.h:120 #2 do_wait (val=12, addr=0x9841bbd4) at ../../../src/libgomp/config/linux/wait.h:64 #3 gomp_barrier_wait_end (bar=0x9841bbd0, state=12) at ../../../src/libgomp/config/linux/bar.c:47 #4 0xb3904db8 in gomp_barrier_wait (bar=bar@entry=0x9841bbd0) at ../../../src/libgomp/config/linux/bar.c:55 #5 0xb390343c in gomp_thread_start (xdata=0x96512630) at ../../../src/libgomp/team.c:120 #6 0xb34b6c39 in start_thread (arg=0x94effb70) at pthread_create.c:304 #7 0xb4a2578e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130 Thread 1 (Thread 0xae9568c0 (LWP 15920)): #0 0xb76f9424 in __kernel_vsyscall () #1 0xb34bb20a in __pthread_cond_wait (cond=0xa0cc940, mutex=0xa0cc928) at pthread_cond_wait.c:153 #2 0xb4a3287d in __pthread_cond_wait (cond=0xa0cc940, mutex=0xa0cc928) at forward.c:139 #3 0xb4cd1470 in wait (time=4294967295, this=0xa0cc928) at thread/qwaitcondition_unix.cpp:86 #4 QWaitCondition::wait (this=0xa0cae4c, mutex=0xa0cae48, time=4294967295) at thread/qwaitcondition_unix.cpp:158 #5 0xb69dea54 in Digikam::DynamicThread::wait(QMutexLocker&) () from /usr/lib/libdigikamcore.so.3 #6 0xb69ded09 in Digikam::DynamicThread::shutDown() () from /usr/lib/libdigikamcore.so.3 #7 0xb69a4338 in Digikam::ManagedLoadSaveThread::shutDown() () from /usr/lib/libdigikamcore.so.3 #8 0xb69bfa91 in Digikam::ThumbnailLoadThread::~ThumbnailLoadThread() () from /usr/lib/libdigikamcore.so.3 #9 0xb69bfc02 in Digikam::ThumbnailLoadThread::~ThumbnailLoadThread() () from /usr/lib/libdigikamcore.so.3 #10 0xb69bd5a2 in ?? () from /usr/lib/libdigikamcore.so.3 #11 0xb67decf9 in ?? () from /usr/lib/libdigikamcore.so.3 #12 0xb497f50f in __run_exit_handlers (status=1, listp=0xb4aaf324, run_list_atexit=true) at exit.c:78 #13 0xb497f57f in *__GI_exit (status=1) at exit.c:100 #14 0xb53ed668 in qt_xio_errhandler () at kernel/qapplication_x11.cpp:770 #15 0xb5f11289 in KApplication::xioErrhandler(_XDisplay*) () from /usr/lib/libkdeui.so.5 #16 0xb5f112c4 in ?? () from /usr/lib/libkdeui.so.5 #17 0xb4563c74 in _XIOError () from /usr/lib/i386-linux-gnu/libX11.so.6 #18 0xb456157f in _XEventsQueued () from /usr/lib/i386-linux-gnu/libX11.so.6 #19 0xb4552080 in XEventsQueued () from /usr/lib/i386-linux-gnu/libX11.so.6 #20 0xb5429ffa in x11EventSourceCheck (s=s@entry=0x9b5ea00) at kernel/qguieventdispatcher_glib.cpp:85 #21 0xb31924bf in g_main_context_check (context=context@entry=0x9b5c100, max_priority=<optimized out>, fds=fds@entry=0x945c9e70, n_fds=n_fds@entry=15) at /build/buildd-glib2.0_2.33.12+really2.32.4-5-i386-eISom6/glib2.0-2.33.12+really2.32.4/./glib/gmain.c:3023 #22 0xb3192982 in g_main_context_iterate (context=context@entry=0x9b5c100, block=block@entry=1, dispatch=dispatch@entry=1, self=<error reading variable: Unhandled dwarf expression opcode 0xfa>) at /build/buildd-glib2.0_2.33.12+really2.32.4-5-i386-eISom6/glib2.0-2.33.12+really2.32.4/./glib/gmain.c:3143 #23 0xb3192b51 in g_main_context_iteration (context=0x9b5c100, may_block=1) at /build/buildd-glib2.0_2.33.12+really2.32.4-5-i386-eISom6/glib2.0-2.33.12+really2.32.4/./glib/gmain.c:3207 #24 0xb4e14831 in QEventDispatcherGlib::processEvents (this=0x9b167c8, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #25 0xb542a1fa in QGuiEventDispatcherGlib::processEvents (this=0x9b167c8, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #26 0xb4de101c in QEventLoop::processEvents (this=this@entry=0xbfeede08, flags=...) at kernel/qeventloop.cpp:149 #27 0xb4de1311 in QEventLoop::exec (this=0xbfeede08, flags=...) at kernel/qeventloop.cpp:204 #28 0xb4de6a8a in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1187 #29 0xb53752f4 in QApplication::exec () at kernel/qapplication.cpp:3817 #30 0x080c2966 in ?? () #31 0xb4966e46 in __libc_start_main (main=0x80c15b0, argc=5, ubp_av=0xbfeee174, init=0x842c6c0 <__libc_csu_init>, fini=0x842c6b0 <__libc_csu_fini>, rtld_fini=0xb7708590, stack_end=0xbfeee16c) at libc-start.c:228 #32 0x080c4d99 in _start () Possible duplicates by query: bug 320249, bug 320154, bug 319948, bug 319882, bug 319745. Reported using DrKonqi -- 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 |
https://bugs.kde.org/show_bug.cgi?id=320253
--- Comment #1 from Jekyll Wu <[hidden email]> --- Please follow the guide[1] and try to provide a better backtrace, since you can reproduce the crash every time. [1] http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_when_an_uncaught_exception_is_causing_a_crash -- 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 |
In reply to this post by ejovrh
https://bugs.kde.org/show_bug.cgi?id=320253
Gilles Caulier <[hidden email]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[hidden email] Component|general |Thumbnails -- 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 |
In reply to this post by ejovrh
https://bugs.kde.org/show_bug.cgi?id=320253
--- Comment #2 from ejovrh <[hidden email]> --- Created attachment 80064 --> https://bugs.kde.org/attachment.cgi?id=80064&action=edit New crash information added by DrKonqi digikam (3.1.0) on KDE Platform 4.8.4 (4.8.4) using Qt 4.8.2 - What I was doing when the application crashed: scan as before, this time with installed libstdc++ dbg package please advise on the missing dbg symbols. feel free to contact me to reproduce more. -- Backtrace (Reduced): #9 0xb4be228d in __gnu_cxx::__verbose_terminate_handler () at ../../../../src/libstdc++-v3/libsupc++/vterminate.cc:95 #10 0xb4bdfef3 in __cxxabiv1::__terminate (handler=0xb4be2140 <__gnu_cxx::__verbose_terminate_handler()>) at ../../../../src/libstdc++-v3/libsupc++/eh_terminate.cc:40 #11 0xb4bdff2f in std::terminate () at ../../../../src/libstdc++-v3/libsupc++/eh_terminate.cc:50 #12 0xb4be0225 in __cxxabiv1::__cxa_rethrow () at ../../../../src/libstdc++-v3/libsupc++/eh_throw.cc:116 #13 0xb4d5eae2 in QThreadPoolThread::run (this=0xaa0dd58) at concurrent/qthreadpool.cpp:114 -- 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 |
In reply to this post by ejovrh
https://bugs.kde.org/show_bug.cgi?id=320253
Jekyll Wu <[hidden email]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEEDSINFO Resolution|--- |BACKTRACE --- Comment #3 from Jekyll Wu <[hidden email]> --- @ejovrh, please read comment #1. Drkonqi can't generate a useful backtrace in your case. You have to run digikam under gdb. -- 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 |
In reply to this post by ejovrh
https://bugs.kde.org/show_bug.cgi?id=320253
--- Comment #4 from Marcel Wiesweg <[hidden email]> --- In fact we need the place where the exception is thrown. That means you need to run digikam under gdb, interrupt, "catch throw", provoke the crash, and get the backtrace. -- 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 |
In reply to this post by ejovrh
https://bugs.kde.org/show_bug.cgi?id=320253
--- Comment #5 from Jekyll Wu <[hidden email]> --- Yes, just follow the guide given in comment #1. -- 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 |
In reply to this post by ejovrh
https://bugs.kde.org/show_bug.cgi?id=320253
Gilles Caulier <[hidden email]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDSINFO |RESOLVED -- 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 |
In reply to this post by ejovrh
https://bugs.kde.org/show_bug.cgi?id=320253
--- Comment #6 from Gilles Caulier <[hidden email]> --- New digiKam 4.11.0 is available with official PKG installer for OSX. https://www.digikam.org/node/740 Can you reproduce the problem with this release ? -- 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 |
In reply to this post by ejovrh
https://bugs.kde.org/show_bug.cgi?id=320253
--- Comment #7 from Gilles Caulier <[hidden email]> --- digiKam 4.12.0 is out : https://www.digikam.org/node/741 We need a fresh feedback using this release please... Thanks in advance. 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 |
In reply to this post by ejovrh
https://bugs.kde.org/show_bug.cgi?id=320253
[hidden email] changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|BACKTRACE |FIXED Version Fixed In| |5.1.0 --- Comment #8 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 |
In reply to this post by ejovrh
https://bugs.kde.org/show_bug.cgi?id=320253
[hidden email] changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Thumbs-Image |Thumbs-Engine -- You are receiving this mail because: You are the assignee for the bug. |
Free forum by Nabble | Edit this page |