Bug 275452 - showFoto crashed during crop process (Scheren in German)
Summary: showFoto crashed during crop process (Scheren in German)
Status: RESOLVED NOT A BUG
Alias: None
Product: digikam
Classification: Applications
Component: Showfoto-Plugins (show other bugs)
Version: 1.8.0
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-12 11:08 UTC by Sebastian
Modified: 2022-02-05 04:42 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In: 7.6.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sebastian 2011-06-12 11:08:23 UTC
Application: showfoto (1.8.0)
KDE Platform Version: 4.6.00 (4.6.0) "release 6"
Qt Version: 4.7.1
Operating System: Linux 2.6.37.6-0.5-desktop i686
Distribution: "openSUSE 11.4 (i586)"

-- Information about the crash:
- What I was doing when the application crashed:
-- I did open a picture in showFoto: OK
-- I used the command Transforming --> Crop (Transformieren --> Scheren): OK
-- I tuned the red lines to the correct position: OK
-- I pushed the bottom ok: CRASH

The crash can be reproduced every time.

-- Backtrace:
Application: showFoto (showfoto), signal: Segmentation fault
[Current thread is 1 (Thread 0xb287c740 (LWP 6485))]

Thread 3 (Thread 0xafb1bb70 (LWP 6487)):
#0  0xffffe424 in __kernel_vsyscall ()
#1  0xb598803e in poll () from /lib/libc.so.6
#2  0xb46660bb in g_poll () from /lib/libglib-2.0.so.0
#3  0xb4655c46 in ?? () from /lib/libglib-2.0.so.0
#4  0xb4655fce in g_main_context_iteration () from /lib/libglib-2.0.so.0
#5  0xb67a97b7 in QEventDispatcherGlib::processEvents (this=0x82d9900, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#6  0xb677a2bd in QEventLoop::processEvents (this=0xafb1b280, flags=...) at kernel/qeventloop.cpp:149
#7  0xb677a4e9 in QEventLoop::exec (this=0xafb1b280, flags=...) at kernel/qeventloop.cpp:201
#8  0xb667b7b9 in QThread::exec (this=0x82d7ba8) at thread/qthread.cpp:490
#9  0xb675a23d in QInotifyFileSystemWatcherEngine::run (this=0x82d7ba8) at io/qfilesystemwatcher_inotify.cpp:248
#10 0xb667e3aa in QThreadPrivate::start (arg=0x82d7ba8) at thread/qthread_unix.cpp:285
#11 0xb5297b05 in start_thread () from /lib/libpthread.so.0
#12 0xb5992d5e in clone () from /lib/libc.so.6

Thread 2 (Thread 0xaf140b70 (LWP 6499)):
[KCrash Handler]
#7  0xb74576fb in Digikam::PixelsAliasFilter::pixelAntiAliasing (this=0xaf1401ef, data=0x2290b008 "\001\001\001\377", Width=10200, Height=14032, X=-3.7163104147849846e-10, Y=-2.7014229069845241e-10, A=0x3 <Address 0x3 out of bounds>, R=0x2 <Address 0x2 out of bounds>, G=0x1 <Address 0x1 out of bounds>, B=0x0) at /usr/src/debug/digikam-1.8.0/libs/dimg/filters/fx/pixelsaliasfilter.cpp:94
#8  0xb74cfc51 in Digikam::ShearFilter::filterImage (this=0x8fe0038) at /usr/src/debug/digikam-1.8.0/libs/dimg/filters/transform/shearfilter.cpp:153
#9  0xb742dac0 in Digikam::DImgThreadedFilter::startFilterDirectly (this=0x8fe0038) at /usr/src/debug/digikam-1.8.0/libs/dimg/filters/dimgthreadedfilter.cpp:146
#10 0xb742d63f in Digikam::DImgThreadedFilter::run (this=0x8fe0038) at /usr/src/debug/digikam-1.8.0/libs/dimg/filters/dimgthreadedfilter.cpp:167
#11 0xb75bd2d6 in Digikam::DynamicThread::DynamicThreadPriv::run (this=0x839c010) at /usr/src/debug/digikam-1.8.0/libs/threads/dynamicthread.cpp:306
#12 0xb6673d63 in QThreadPoolThread::run (this=0x8d1d920) at concurrent/qthreadpool.cpp:106
#13 0xb667e3aa in QThreadPrivate::start (arg=0x8d1d920) at thread/qthread_unix.cpp:285
#14 0xb5297b05 in start_thread () from /lib/libpthread.so.0
#15 0xb5992d5e in clone () from /lib/libc.so.6

Thread 1 (Thread 0xb287c740 (LWP 6485)):
#0  0xffffe424 in __kernel_vsyscall ()
#1  0xb529c105 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#2  0xb59a0aec in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libc.so.6
#3  0xb667eab0 in wait (this=0x820859c, mutex=0x8208588, time=4294967295) at thread/qwaitcondition_unix.cpp:88
#4  QWaitCondition::wait (this=0x820859c, mutex=0x8208588, time=4294967295) at thread/qwaitcondition_unix.cpp:160
#5  0xb6673402 in QThreadPoolPrivate::waitForDone (this=0x8208538) at concurrent/qthreadpool.cpp:295
#6  0xb66743a0 in QThreadPool::~QThreadPool (this=0x827bd40, __in_chrg=<value optimized out>) at concurrent/qthreadpool.cpp:428
#7  0xb6674402 in QThreadPool::~QThreadPool (this=0x827bd40, __in_chrg=<value optimized out>) at concurrent/qthreadpool.cpp:430
#8  0xb678ed24 in QObjectPrivate::deleteChildren (this=0x820d630) at kernel/qobject.cpp:1949
#9  0xb6793bac in QObject::~QObject (this=0x827b860, __in_chrg=<value optimized out>) at kernel/qobject.cpp:945
#10 0xb75ba9a8 in Digikam::ThreadManager::~ThreadManager (this=0x827b860, __in_chrg=<value optimized out>) at /usr/src/debug/digikam-1.8.0/libs/threads/threadmanager.cpp:246
#11 0xb75baa39 in ~ThreadManagerCreator () at /usr/src/debug/digikam-1.8.0/libs/threads/threadmanager.cpp:226
#12 destroy () at /usr/src/debug/digikam-1.8.0/libs/threads/threadmanager.cpp:230
#13 0xb747a319 in KCleanUpGlobalStatic::~KCleanUpGlobalStatic (this=0xb7772578, __in_chrg=<value optimized out>) at /usr/include/kglobal.h:62
#14 0xb58ed89f in __run_exit_handlers () from /lib/libc.so.6
#15 0xb58ed8fd in exit () from /lib/libc.so.6
#16 0xb5d1c1c8 in ?? () from /usr/lib/libQtGui.so.4
#17 0xb6c89c49 in KApplication::xioErrhandler(_XDisplay*) () from /usr/lib/libkdeui.so.5
#18 0xb6c89c84 in ?? () from /usr/lib/libkdeui.so.5
#19 0xb4ed34c4 in _XIOError () from /usr/lib/libX11.so.6
#20 0xb4ed0c9f in _XEventsQueued () from /usr/lib/libX11.so.6
#21 0xb4ec1458 in XPending () from /usr/lib/libX11.so.6
#22 0xb5d2fd54 in ?? () from /usr/lib/libQtGui.so.4
#23 0xb5d2f13e in QApplication::x11ProcessEvent(_XEvent*) () from /usr/lib/libQtGui.so.4
#24 0xb5d59960 in ?? () from /usr/lib/libQtGui.so.4
#25 0xb4655509 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#26 0xb4655d10 in ?? () from /lib/libglib-2.0.so.0
#27 0xb4655fce in g_main_context_iteration () from /lib/libglib-2.0.so.0
#28 0xb67a976b in QEventDispatcherGlib::processEvents (this=0x80a8ab8, flags=...) at kernel/qeventdispatcher_glib.cpp:422
#29 0xb5d5955a in ?? () from /usr/lib/libQtGui.so.4
#30 0xb677a2bd in QEventLoop::processEvents (this=0xbf95d3f4, flags=...) at kernel/qeventloop.cpp:149
#31 0xb677a4e9 in QEventLoop::exec (this=0xbf95d3f4, flags=...) at kernel/qeventloop.cpp:201
#32 0xb677ef90 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009
#33 0xb5ca1104 in QApplication::exec() () from /usr/lib/libQtGui.so.4
#34 0x0807141f in main (argc=) at /usr/src/debug/digikam-1.8.0/showfoto/main.cpp:89

Reported using DrKonqi
Comment 1 caulier.gilles 2011-06-12 11:12:51 UTC
Very strange crash. I never see code to crash here...

Can you test again using last stable 1.9.0 ?

Best

Gilles Caulier
Comment 2 Sebastian 2011-06-12 17:42:01 UTC
Dear Gilles,

thanks for your fast reply.
Opensuse 11.4 only provides 1.8.0 so far. I am not sure to be able to  
install the 1.9.0 version via tarball (at least not now, I need more time  
to do so).

So, if this is a strange crash - maybe I did something wrong?

Anyway, if you want me to install 1.9.0, I'll try to install.

Best regards,
Sebastian


Am 12.06.2011, 11:12 Uhr, schrieb Gilles Caulier  
<caulier.gilles@gmail.com>:

> https://bugs.kde.org/show_bug.cgi?id=275452
>
>
> Gilles Caulier <caulier.gilles@gmail.com> changed:
>
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                  CC|                            |caulier.gilles@gmail.com
>
>
>
>
> --- Comment #1 from Gilles Caulier <caulier gilles gmail com>   
> 2011-06-12 11:12:51 ---
> Very strange crash. I never see code to crash here...
>
> Can you test again using last stable 1.9.0 ?
>
> Best
>
> Gilles Caulier
>
Comment 3 Marcel Wiesweg 2011-06-18 14:42:12 UTC
Does this mean you can crash the filter with each picture and every time?
Comment 4 Sebastian 2011-07-28 05:44:49 UTC
Good morning,

I tried to reproduce the crash on an other computer with same opensuse/kde  
version. Here, everything was all right.
Therefore, I recommend to close this topic, since it seems to be a  
hardware-specific topic.

Best regards,
Sebastian

Am 18.06.2011, 14:42 Uhr, schrieb Marcel Wiesweg <marcel.wiesweg@gmx.de>:

> https://bugs.kde.org/show_bug.cgi?id=275452
>
>
>
>
>
> --- Comment #3 from Marcel Wiesweg <marcel wiesweg gmx de>  2011-06-18  
> 14:42:12 ---
> Does this mean you can crash the filter with each picture and every time?
>