Bug 251240 - 100% cpu load
Summary: 100% cpu load
Status: RESOLVED DUPLICATE of bug 235607
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: 1.13.3
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-14 20:45 UTC by BRULE Herman
Modified: 2011-05-18 14:22 UTC (History)
3 users (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 BRULE Herman 2010-09-14 20:45:05 UTC
Version:           1.13.3 (using KDE 4.5.1) 
OS:                Linux

Hello, after few minutes kmail use 100% of one cpu, I have multiple account, and I have upgraded from KDE 4.4, the backtrace after attached process to gdb:

#0  QHash<QGesture*, QGestureRecognizer*>::findNode (this=0x220b388, akey=@0x7fffeec42228, ahp=0x0) at ../../include/QtCore/../../src/corelib/tools/qhash.h:877
#1  0x00007ffcc2a0d8ea in QHash<QGesture*, QGestureRecognizer*>::contains (this=0x220b350, receiver=0x26a4ac0, event=0x7fffeec427a0) at ../../include/QtCore/../../src/corelib/tools/qhash.h:867
#2  QGestureManager::filterEvent (this=0x220b350, receiver=0x26a4ac0, event=0x7fffeec427a0) at kernel/qgesturemanager.cpp:511
#3  0x00007ffcc29927b8 in QApplication::notify (this=0x7fffeec42c10, receiver=0x26a4ac0, e=0x7fffeec427a0) at kernel/qapplication.cpp:3678
#4  0x00007ffcc51bb9c1 in KApplication::notify (this=0x7fffeec42c10, receiver=0x26a4ac0, event=0x7fffeec427a0) at /var/tmp/portage/kde-base/kdelibs-4.5.1/work/kdelibs-4.5.1/kdeui/kernel/kapplication.cpp:310
#5  0x00007ffcc372150b in QCoreApplication::notifyInternal (this=0x7fffeec42c10, receiver=0x26a4ac0, event=0x7fffeec427a0) at kernel/qcoreapplication.cpp:726
#6  0x00007ffcc3756a62 in QCoreApplication::sendEvent (this=0x1d25c20) at kernel/qcoreapplication.h:215
#7  QTimerInfoList::activateTimers (this=0x1d25c20) at kernel/qeventdispatcher_unix.cpp:603
#8  0x00007ffcc37531d8 in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:184
#9  idleTimerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:231
#10 0x00007ffcb94cc83f in g_main_dispatch (context=0x1d24c80) at gmain.c:1960
#11 IA__g_main_context_dispatch (context=0x1d24c80) at gmain.c:2513
#12 0x00007ffcb94d0bf8 in g_main_context_iterate (context=0x1d24c80, block=<value optimized out>, dispatch=<value optimized out>, self=<value optimized out>) at gmain.c:2591
#13 0x00007ffcb94d0dac in IA__g_main_context_iteration (context=0x1d24c80, may_block=1) at gmain.c:2654
#14 0x00007ffcc3752df3 in QEventDispatcherGlib::processEvents (this=0x1d15e30, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:412
#15 0x00007ffcc2a5506e in QGuiEventDispatcherGlib::processEvents (this=0x220b388, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#16 0x00007ffcc371f8b2 in QEventLoop::processEvents (this=<value optimized out>, flags=DWARF-2 expression error: DW_OP_reg operations must be used either alone or in conjuction with DW_OP_piece.
) at kernel/qeventloop.cpp:149
#17 0x00007ffcc371fd55 in QEventLoop::exec (this=0x7fffeec42a40, flags=DWARF-2 expression error: DW_OP_reg operations must be used either alone or in conjuction with DW_OP_piece.
) at kernel/qeventloop.cpp:201
#18 0x00007ffcc372283b in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1003
#19 0x00000000004037f2 in main (argc=<value optimized out>, argv=<value optimized out>) at /var/tmp/portage/kde-base/kmail-4.4.5/work/kmail-4.4.5/kmail/main.cpp:156


Reproducible: Always
Comment 1 Nikos Papas 2010-09-15 17:54:59 UTC
This could be related to:

https://bugs.kde.org/show_bug.cgi?id=243569
Comment 2 BRULE Herman 2010-09-15 20:30:33 UTC
I don't know, for me, I can write mail, the system is not really more slow. When I restart kmail, it use 0% for few time, after re-use 100% of cpu.
Comment 3 Christophe Marin 2011-05-18 14:22:07 UTC
Merging with 235607

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