Bug 192983 - Plasma crashes on window minimize/maximize (Plasma::Animator::timerEvent)
Summary: Plasma crashes on window minimize/maximize (Plasma::Animator::timerEvent)
Status: RESOLVED DUPLICATE of bug 192066
Alias: None
Product: plasma4
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Unspecified
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-17 12:06 UTC by msnkipa
Modified: 2009-06-02 20:11 UTC (History)
3 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description msnkipa 2009-05-17 12:06:10 UTC
Version:            (using Devel)
Installed from:    Compiled sources

When I minimize and them maximize windows plasma crashes. I have my own QT program, there are first QDialog that launch second QDialog. I minimize First dialog by press button in the dialog border. All dialogs minimizes (is it correct?) than I maximize second dialog from tray and in that moment plasma crashes.

backtrace:
Application: Plasma Workspace (kdeinit), signal: Floating point exception
[Current thread is 0 (LWP 4173)]

Thread 2 (Thread 0x7f122858e950 (LWP 4178)):
#0  0x00007f1247a84d59 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x00007f1247d0aa61 in QWaitConditionPrivate::wait (this=0xdd9f40, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:87
#2  0x00007f1247d0a80a in QWaitCondition::wait (this=0xdccf90, mutex=0xdccf88, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:159
#3  0x00007f124689cf0a in QHostInfoAgent::run (this=0xdccf70) at kernel/qhostinfo.cpp:260
#4  0x00007f1247d0969d in QThreadPrivate::start (arg=0xdccf70) at thread/qthread_unix.cpp:189
#5  0x00007f1247a81070 in start_thread () from /lib64/libpthread.so.0
#6  0x00007f12442d60ed in clone () from /lib64/libc.so.6
#7  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f12482f5760 (LWP 4173)):
[KCrash Handler]
#5  0x00007f123f2658f6 in Plasma::Animator::timerEvent (this=<value optimized out>, event=<value optimized out>) at /home/kde-devel/kde/src/KDE/kdelibs/plasma/animator.cpp:661
#6  0x00007f1247e1ea4b in QObject::event (this=0x7cce20, e=0x7fff50342900) at kernel/qobject.cpp:1082
#7  0x00007f1244edafe6 in QApplicationPrivate::notify_helper (this=0x677600, receiver=0x7cce20, e=0x7fff50342900) at kernel/qapplication.cpp:4084
#8  0x00007f1244ed9287 in QApplication::notify (this=0x66e880, receiver=0x7cce20, e=0x7fff50342900) at kernel/qapplication.cpp:3631
#9  0x00007f12461a1a56 in KApplication::notify (this=0x66e880, receiver=0x7cce20, event=0x7fff50342900) at /home/kde-devel/kde/src/KDE/kdelibs/kdeui/kernel/kapplication.cpp:307
#10 0x00007f1247e096b9 in QCoreApplication::notifyInternal (this=0x66e880, receiver=0x7cce20, event=0x7fff50342900) at kernel/qcoreapplication.cpp:598
#11 0x00007f1247e0cc1f in QCoreApplication::sendEvent (receiver=0x7cce20, event=0x7fff50342900) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#12 0x00007f1247e3f34e in QTimerInfoList::activateTimers (this=0x67a970) at kernel/qeventdispatcher_unix.cpp:572
#13 0x00007f1247e3b6b3 in timerSourceDispatch (source=0x67a910) at kernel/qeventdispatcher_glib.cpp:164
#14 0x00007f12439540db in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#15 0x00007f12439578ad in ?? () from /usr/lib64/libglib-2.0.so.0
#16 0x00007f1243957a6b in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#17 0x00007f1247e3c55d in QEventDispatcherGlib::processEvents (this=0x676ef0, flags={i = 36}) at kernel/qeventdispatcher_glib.cpp:323
#18 0x00007f1244f870ac in QGuiEventDispatcherGlib::processEvents (this=0x676ef0, flags={i = 36}) at kernel/qguieventdispatcher_glib.cpp:202
#19 0x00007f1247e070d8 in QEventLoop::processEvents (this=0x7fff50342c50, flags={i = 36}) at kernel/qeventloop.cpp:149
#20 0x00007f1247e07212 in QEventLoop::exec (this=0x7fff50342c50, flags={i = 0}) at kernel/qeventloop.cpp:196
#21 0x00007f1247e09d78 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:880
#22 0x00007f1244ed8ece in QApplication::exec () at kernel/qapplication.cpp:3553
#23 0x00007f123c0b3e3f in kdemain (argc=<value optimized out>, argv=<value optimized out>) at /home/kde-devel/kde/src/KDE/kdebase/workspace/plasma/shells/desktop/main.cpp:50
#24 0x0000000000407115 in launch (argc=1, _name=<value optimized out>, args=<value optimized out>, cwd=<value optimized out>, envc=0, envs=0x6523e7 "", reset_env=false, tty=0x0, avoid_loops=false, 
    startup_id_str=0x40a98e "0") at /home/kde-devel/kde/src/KDE/kdelibs/kinit/kinit.cpp:667
#25 0x0000000000407f8b in handle_launcher_request (sock=7, who=<value optimized out>) at /home/kde-devel/kde/src/KDE/kdelibs/kinit/kinit.cpp:1159
#26 0x000000000040856c in handle_requests (waitForPid=<value optimized out>) at /home/kde-devel/kde/src/KDE/kdelibs/kinit/kinit.cpp:1352
#27 0x0000000000408cd3 in main (argc=2, argv=<value optimized out>, envp=<value optimized out>) at /home/kde-devel/kde/src/KDE/kdelibs/kinit/kinit.cpp:1779
Comment 1 Dario Andres 2009-05-17 16:25:45 UTC
Hi. What is your KDE version (svn revision/branch)

I tried to recreate the testcase (a simple app with two QDialogs), but I couldn't reproduce the crash. Could you upload the testcase (if it doesn't contain private information), so we can test it ?

Thanks a lot!
Comment 2 Aaron J. Seigo 2009-05-18 11:49:35 UTC
also, can you please provide a testcase for this, such as your Qt app? things like "maximize from tray" are a bit ambiguous (from the tasks widget? from the system tray?). it would be good to test using an exact example of what causes the crash for you.
Comment 3 msnkipa 2009-05-18 22:04:49 UTC
I`m very sorry but I can`t provide the testcase app as it is a part of big private project that I work on. But, I have recompiled KDE with gcc 4.4.1 prerelease, not 4.5.0 experimental and now I can`t reproduce this bug... Mabye some magic from gcc with it`s -O2 optimization...
Comment 4 Marco Martin 2009-06-02 20:11:29 UTC

*** This bug has been marked as a duplicate of bug 192066 ***