https://bugs.kde.org/show_bug.cgi?id=225602
--- Comment #12 from Martin L ü c h e m <Heinrich20 gmx de> 2010-04-15 15:34:48 --- Hi Thomas, the situation improved a little bit. Some weeks everything seemed to be ok but then the problem reoccured. Now we have CPU usage up to 20%. This occurs in cycles! This is the result of GDB. I hope, what I did is correct and helps: Program received signal SIGINT, Interrupt. 0x00007fe43e12c743 in *__GI___poll (fds=<value optimized out>, nfds=<value optimized out>, timeout=3024) at ../sysdeps/unix/sysv/linux/poll.c:87 87 in ../sysdeps/unix/sysv/linux/poll.c (gdb) backtrace #0 0x00007fe43e12c743 in *__GI___poll (fds=<value optimized out>, nfds=<value optimized out>, timeout=3024) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x00007fe4365ac299 in ?? () from /lib/libglib-2.0.so.0 #2 0x00007fe4365ac6ec in g_main_context_iteration () from /lib/libglib-2.0.so.0 #3 0x00007fe43f66d39c in QEventDispatcherGlib::processEvents (this=0xbb9b40, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:407 #4 0x00007fe43eb54f1f in QGuiEventDispatcherGlib::processEvents (this=0x2a74600, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202 #5 0x00007fe43f643562 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149 #6 0x00007fe43f643934 in QEventLoop::exec (this=0x7fff597d8f20, flags=...) at kernel/qeventloop.cpp:201 #7 0x00007fe43f645ba4 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #8 0x0000000000402fa9 in main (argc=<value optimized out>, argv=<value optimized out>) at ../../kmail/main.cpp:146 (gdb) next interrupt: Continuing. [New Thread 0x7fe4261b2910 (LWP 13205)] [Thread 0x7fe4261b2910 (LWP 13205) exited] [New Thread 0x7fe4261b2910 (LWP 13225)] [Thread 0x7fe4261b2910 (LWP 13225) exited] ^C Program received signal SIGINT, Interrupt. 0x00007fe43e12c743 in *__GI___poll (fds=<value optimized out>, nf ds=<value optimized out>, timeout=4989) at ../sysdeps/unix/sysv/linux/poll.c:87 87 in ../sysdeps/unix/sysv/linux/poll.c (gdb) backtrace #0 0x00007fe43e12c743 in *__GI___poll (fds=<value optimized out>, nfds=<value optimized out>, timeout=4989) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x00007fe4365ac299 in ?? () from /lib/libglib-2.0.so.0 #2 0x00007fe4365ac6ec in g_main_context_iteration () from /lib/libglib-2.0.so.0 #3 0x00007fe43f66d39c in QEventDispatcherGlib::processEvents (this=0xbb9b40, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:407 #4 0x00007fe43eb54f1f in QGuiEventDispatcherGlib::processEvents (this=0x2a74600, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202 #5 0x00007fe43f643562 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149 #6 0x00007fe43f643934 in QEventLoop::exec (this=0x7fff597d8f20, flags=...) at kernel/qeventloop.cpp:201 #7 0x00007fe43f645ba4 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #8 0x0000000000402fa9 in main (argc=<value optimized out>, argv=<value optimized out>) at ../../kmail/main.cpp:146 (gdb) next interrupt: Program received signal SIGINT, Interrupt. 0x00007fe43e12c743 in *__GI___poll (fds=<value optimized out>, nf ds=<value optimized out>, timeout=8540) at ../sysdeps/unix/sysv/linux/poll.c:87 87 in ../sysdeps/unix/sysv/linux/poll.c (gdb) backtrace #0 0x00007fe43e12c743 in *__GI___poll (fds=<value optimized out>, nfds=<value optimized out>, timeout=8540) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x00007fe4365ac299 in ?? () from /lib/libglib-2.0.so.0 #2 0x00007fe4365ac6ec in g_main_context_iteration () from /lib/libglib-2.0.so.0 #3 0x00007fe43f66d39c in QEventDispatcherGlib::processEvents (this=0xbb9b40, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:407 #4 0x00007fe43eb54f1f in QGuiEventDispatcherGlib::processEvents (this=0x2a74600, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202 #5 0x00007fe43f643562 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149 #6 0x00007fe43f643934 in QEventLoop::exec (this=0x7fff597d8f20, flags=...) at kernel/qeventloop.cpp:201 #7 0x00007fe43f645ba4 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #8 0x0000000000402fa9 in main (argc=<value optimized out>, argv=<value optimized out>) at ../../kmail/main.cpp:146 (gdb) next interrupt: Continuing. [New Thread 0x7fe4261b2910 (LWP 13241)] [Thread 0x7fe4261b2910 (LWP 13241) exited] [New Thread 0x7fe4261b2910 (LWP 13270)] [Thread 0x7fe4261b2910 (LWP 13270) exited] [New Thread 0x7fe4261b2910 (LWP 13312)] [Thread 0x7fe4261b2910 (LWP 13312) exited] [New Thread 0x7fe4261b2910 (LWP 13344)] [Thread 0x7fe4261b2910 (LWP 13344) exited] [New Thread 0x7fe4261b2910 (LWP 13361)] [New Thread 0x7fe424b60910 (LWP 13362)] ^C Program received signal SIGINT, Interrupt. 0x00007fe43e12c743 in *__GI___poll (fds=<value optimized out>, nf ds=<value optimized out>, timeout=29999) at ../sysdeps/unix/sysv/linux/poll.c:87 87 in ../sysdeps/unix/sysv/linux/poll.c (gdb) backtrace #0 0x00007fe43e12c743 in *__GI___poll (fds=<value optimized out>, nfds=<value optimized out>, timeout=29999) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x00007fe4365ac299 in ?? () from /lib/libglib-2.0.so.0 #2 0x00007fe4365ac6ec in g_main_context_iteration () from /lib/libglib-2.0.so.0 #3 0x00007fe43f66d39c in QEventDispatcherGlib::processEvents (this=0xbb9b40, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:407 #4 0x00007fe43eb54f1f in QGuiEventDispatcherGlib::processEvents (this=0x2a74600, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202 #5 0x00007fe43f643562 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149 #6 0x00007fe43f643934 in QEventLoop::exec (this=0x7fff597d6560, flags=...) at kernel/qeventloop.cpp:201 #7 0x00007fe43ef46c7e in QDialog::exec (this=0x7fff597d65f0) at dialogs/qdialog.cpp:498 #8 0x00007fe43fe1d48a in KMComposeWin::slotAttachFile (this=0x3a4df50) at ../../kmail/kmcomposewin.cpp:2283 #9 0x00007fe43fe3f1c1 in KMComposeWin::qt_metacall (this=0x3a4df50, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff597d68c0) at ./kmcomposewin.moc:236 #10 0x00007fe43f659df2 in QMetaObject::activate (sender=0x3b38bb0, from_signal_index=<value optimized out>, to_signal_index=6, argv=0xffffffffffffffff) at kernel/qobject.cpp:3112 #11 0x00007fe43eab8147 in QAction::triggered (this=0x2a74600, _t1=false) at .moc/release-shared/moc_qaction.cpp:236 #12 0x00007fe43eab95c0 in QAction::activate (this=0x3b38bb0, event=<value optimized out>) at kernel/qaction.cpp:1167 #13 0x00007fe43ee30eda in QAbstractButtonPrivate::click (this=0x3be9fd0) at widgets/qabstractbutton.cpp:525 #14 0x00007fe43ee31175 in QAbstractButton::mouseReleaseEvent (this=0x3bc9900, e=0x7fff597d7220) at widgets/qabstractbutton.cpp:1115 #15 0x00007fe43eeffc2a in QToolButton::mouseReleaseEvent (this=0x2a74600, e=0xe) at widgets/qtoolbutton.cpp:709 #16 0x00007fe43eb0e37f in QWidget::event (this=0x3bc9900, event=0x7fff597d7220) at kernel/qwidget.cpp:7554 #17 0x00007fe43eabe01d in QApplicationPrivate::notify_helper (this=0xc0c140, receiver=0x3bc9900, e=0x7fff597d7220) at kernel/qapplication.cpp:4065 #18 0x00007fe43eac67ca in QApplication::notify (this=<value optimized out>, receiver=0x3bc9900, e=0x7fff597d7220) at kernel/qapplication.cpp:3767 #19 0x00007fe440ce4de6 in KApplication::notify (this=0x7fff597d90d0, receiver=0x3bc9900, event=0x7fff597d7220) ---Type <return> to continue, or q <return> to quit--- Am Dienstag, 2. März 2010, um 23:11:21 schrieb Thomas McGuire: > https://bugs.kde.org/show_bug.cgi?id=225602 > > > > > > --- Comment #11 from Thomas McGuire <mcguire kde org> 2010-03-02 23:11:07 > --- > > > I can try to find out how to use GDB. It is installed at my machine and > > it this should be a good way to finbd out the reason that makes my > > machine slow. > > Ok, this is how you use GDB for this: > > 1. Attach GDB to the KMail process: > gdb --pid `pidof kmail` > 2. When GDB is done attaching, it has interrupted the application. Type > "continue" to let it continue. > 3. Press Ctrl+C at any time time to interrupt the application, and type > "continue" again to let it continue > 4. When KMail is interrupted, type "backtrace" to get a backtrace. That > will show you in which code path KMail currently is. If you manage to > interrupt KMail when it is using CPU, the backtrace should show which > function uses the CPU and how it is called. > Try interrupting KMail several times, when it is using CPU. If the > backtraces have similar function names, then those functions are likely > the ones using the CPU. If you manage to find a backtrace that's nearly > always the same when KMail is using CPU, post it here. > -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs