Bug 224985 - Plasma Workspace slow and crashes shortly after (slowly!) resuming from RAM
Summary: Plasma Workspace slow and crashes shortly after (slowly!) resuming from RAM
Status: RESOLVED DUPLICATE of bug 219036
Alias: None
Product: plasma4
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-31 12:07 UTC by Nikos
Modified: 2010-01-31 13:33 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nikos 2010-01-31 12:07:46 UTC
Application: plasma-desktop (0.3)
KDE Platform Version: 4.3.95 (KDE 4.3.95 (KDE 4.4 RC2))
Qt Version: 4.6.0
Operating System: Linux 2.6.31-18-generic-pae i686
Distribution: Ubuntu 9.10

-- Information about the crash:
After a loooong resume from RAM, during which the system was unresponsive (until the unlock dialog appeared on the screen), the Plasma Workspace was slow (compositing was automatically suspended due to "low performance") and shortly afterwards, Plasma WS crashed.

 -- Backtrace:
Application: Plasma Workspace (kdeinit4), signal: Segmentation fault
[Current thread is 1 (Thread 0xb5648760 (LWP 2774))]

Thread 2 (Thread 0xa540eb70 (LWP 2775)):
#0  0xb78a0430 in __kernel_vsyscall ()
#1  0xb6bf1e15 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/tls/i686/cmov/libpthread.so.0
#2  0xb6c68307 in QWaitConditionPrivate::wait (this=0xa3b0708, mutex=0xa3b0704, time=4294967295) at thread/qwaitcondition_unix.cpp:87
#3  QWaitCondition::wait (this=0xa3b0708, mutex=0xa3b0704, time=4294967295) at thread/qwaitcondition_unix.cpp:159
#4  0xb5e9a102 in QHostInfoAgent::run (this=0xa3b06f8) at kernel/qhostinfo.cpp:252
#5  0xb6c673ae in QThreadPrivate::start (arg=0xa3b06f8) at thread/qthread_unix.cpp:244
#6  0xb6bed80e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#7  0xb60098de in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 1 (Thread 0xb5648760 (LWP 2774)):
[KCrash Handler]
#6  QBasicAtomicInt::deref (this=0xa442a08, __in_chrg=<value optimized out>) at /usr/include/qt4/QtCore/qatomic_i386.h:132
#7  ~QString (this=0xa442a08, __in_chrg=<value optimized out>) at /usr/include/qt4/QtCore/qstring.h:869
#8  0xa65a15ae in ~ForecastInfo (this=0xa2f0e50) at ../../../../../../../plasma/generic/dataengines/weather/ions/bbcukmet/ion_bbcukmet.h:63
#9  UKMETIon::reset (this=0xa2f0e50) at ../../../../../../../plasma/generic/dataengines/weather/ions/bbcukmet/ion_bbcukmet.cpp:53
#10 0xa65c2076 in WeatherEngine::triggerReset (this=0xa2edf20) at ../../../../../plasma/generic/dataengines/weather/weatherengine.cpp:275
#11 0xa65c437b in WeatherEngine::qt_metacall (this=0xa2edf20, _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0xbfd91dfc) at ./weatherengine.moc:93
#12 0xb6d6e11a in QMetaObject::metacall (object=0xa2edf20, cl=173504280, idx=25, argv=0xbfd91dfc) at kernel/qmetaobject.cpp:237
#13 0xb6d7c89b in QMetaObject::activate (sender=0x9f043a0, m=0xb6e7c188, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3294
#14 0xb6d84527 in QSingleShotTimer::timeout (this=0x9f043a0) at .moc/release-shared/qtimer.moc:82
#15 0xb6d8463c in QSingleShotTimer::timerEvent (this=0x9f043a0) at kernel/qtimer.cpp:308
#16 0xb6d79704 in QObject::event (this=0x9f043a0, e=0xa442a08) at kernel/qobject.cpp:1224
#17 0xb62aa19c in QApplicationPrivate::notify_helper (this=0x99bf438, receiver=0x9f043a0, e=0xbfd922c0) at kernel/qapplication.cpp:4242
#18 0xb62b0df7 in QApplication::notify (this=0x99b9390, receiver=0x9f043a0, e=0xbfd922c0) at kernel/qapplication.cpp:3661
#19 0xb705ca1a in KApplication::notify (this=0x99b9390, receiver=0x9f043a0, event=0xbfd922c0) at ../../kdeui/kernel/kapplication.cpp:302
#20 0xb6d68eab in QCoreApplication::notifyInternal (this=0x99b9390, receiver=0x9f043a0, event=0xbfd922c0) at kernel/qcoreapplication.cpp:704
#21 0xb6d98286 in QCoreApplication::sendEvent (this=0x99c14b4) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#22 QTimerInfoList::activateTimers (this=0x99c14b4) at kernel/qeventdispatcher_unix.cpp:603
#23 0xb6d94f17 in timerSourceDispatch (source=0x99c14e8) at kernel/qeventdispatcher_glib.cpp:184
#24 idleTimerSourceDispatch (source=0x99c14e8) at kernel/qeventdispatcher_glib.cpp:231
#25 0xb5a6ee88 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#26 0xb5a72730 in ?? () from /lib/libglib-2.0.so.0
#27 0xb5a72863 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#28 0xb6d94bd5 in QEventDispatcherGlib::processEvents (this=0x99bf228, flags=...) at kernel/qeventdispatcher_glib.cpp:407
#29 0xb6367b75 in QGuiEventDispatcherGlib::processEvents (this=0x99bf228, flags=...) at kernel/qguieventdispatcher_glib.cpp:202
#30 0xb6d674c9 in QEventLoop::processEvents (this=0xbfd92584, flags=) at kernel/qeventloop.cpp:149
#31 0xb6d6791a in QEventLoop::exec (this=0xbfd92584, flags=...) at kernel/qeventloop.cpp:201
#32 0xb6d6bb0f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981
#33 0xb62aa237 in QApplication::exec () at kernel/qapplication.cpp:3570
#34 0xb23f91ee in kdemain (argc=1, argv=0x99ad8c8) at ../../../../plasma/desktop/shell/main.cpp:112
#35 0x0804dff7 in launch (argc=<value optimized out>, _name=<value optimized out>, args=<value optimized out>, cwd=0x0, envc=0, envs=0x9969d30 "", reset_env=false, tty=0x0, avoid_loops=false, 
    startup_id_str=0x8051429 "0") at ../../kinit/kinit.cpp:706
#36 0x0804ec15 in handle_launcher_request (sock=<value optimized out>, who=<value optimized out>) at ../../kinit/kinit.cpp:1198
#37 0x0804f08c in handle_requests (waitForPid=<value optimized out>) at ../../kinit/kinit.cpp:1391
#38 0x0804fe27 in main (argc=4, argv=0xbfd93034, envp=0xbfd93048) at ../../kinit/kinit.cpp:1830

This bug may be a duplicate of or related to bug 224539.

Possible duplicates by query: bug 224539, bug 224483, bug 224222, bug 223538, bug 222116.

Reported using DrKonqi
Comment 1 Dario Andres 2010-01-31 13:33:35 UTC
This issue is being tracked at bug 219036. Regards

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