Bug 191953 - crash (bad free) in Plasma::Animator::timerEvent
Summary: crash (bad free) in 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 Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
: 195444 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-05-07 21:18 UTC by Benoît Jacob
Modified: 2009-06-06 14:12 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 Benoît Jacob 2009-05-07 21:18:52 UTC
Version:            (using Devel)
OS:                Linux
Installed from:    Compiled sources

Hi,

backtrace below. It happened as my laptop had been undergoing 100% cpu usage for a while as i was running a scientific simulation -- maybe that's relevant as the backtrace mentions stuff about timers.

Application : Plasma Workspace (plasma-desktop), signal SIGABRT
[Current thread is 1 (Thread 0xb4926700 (LWP 3628))]

Thread 2 (Thread 0xa9274b90 (LWP 3728)):
#0  0xffffe430 in __kernel_vsyscall ()
#1  0xb6280c35 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#2  0xb62e0722 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQtCore.so.4
#3  0xb77fdae2 in ?? () from /usr/lib/libQtNetwork.so.4
#4  0xb62df70e in ?? () from /usr/lib/libQtCore.so.4
#5  0xb627d1b5 in start_thread () from /lib/libpthread.so.0
#6  0xb60bf3be in clone () from /lib/libc.so.6

Thread 1 (Thread 0xb4926700 (LWP 3628)):
[KCrash Handler]
#6  0xffffe430 in __kernel_vsyscall ()
#7  0xb6018990 in raise () from /lib/libc.so.6
#8  0xb601a2c8 in abort () from /lib/libc.so.6
#9  0xb605a683 in ?? () from /lib/libc.so.6
#10 0xb605bedb in free () from /lib/libc.so.6
#11 0xb623cec1 in operator delete(void*) () from /usr/lib/libstdc++.so.6
#12 0xb7ce2180 in Plasma::Animator::timerEvent(QTimerEvent*) () from /usr/lib/libplasma.so.3
#13 0xb63e426f in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4
#14 0xb665c69c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#15 0xb666499e in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#16 0xb753bc7d in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#17 0xb63d3adb in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4
#18 0xb6403176 in ?? () from /usr/lib/libQtCore.so.4
#19 0xb63ff600 in ?? () from /usr/lib/libQtCore.so.4
#20 0xb4d939c8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#21 0xb4d97083 in ?? () from /usr/lib/libglib-2.0.so.0
#22 0xb4d97241 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#23 0xb63ff558 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#24 0xb66fc975 in ?? () from /usr/lib/libQtGui.so.4
#25 0xb63d20fa in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#26 0xb63d253a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#27 0xb63d49e9 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#28 0xb665c517 in QApplication::exec() () from /usr/lib/libQtGui.so.4
#29 0xb7eb1b00 in kdemain () from /usr/lib/libkdeinit4_plasma-desktop.so
#30 0x08048792 in _start ()
Comment 1 Dario Andres 2009-05-07 22:33:30 UTC
What is your KDE version (svn revision/branch) ?, 
If you can reproduce the crash at will, may you read http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports and post a complete backtrace here? 
This is probably related to bug 190218 / bug 175632
Thanks
Comment 2 Benoît Jacob 2009-05-07 22:38:28 UTC
My KDE version is 4.2.71.svn961800.

Unfortunately, I can't reproduce at will.
Comment 3 Marco Martin 2009-05-12 12:05:46 UTC
marking this as duplicate since the more recent one has a better backtrace

*** This bug has been marked as a duplicate of bug 192066 ***
Comment 4 Dario Andres 2009-06-06 14:12:38 UTC
*** Bug 195444 has been marked as a duplicate of this bug. ***