Bug 132185 - sudden 100% cpu usage in kile
Summary: sudden 100% cpu usage in kile
Status: RESOLVED LATER
Alias: None
Product: kile
Classification: Applications
Component: general (show other bugs)
Version: 1.8.1
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Jeroen Wijnhout
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-08-10 10:01 UTC by Willi Richert
Modified: 2009-01-06 22:27 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 Willi Richert 2006-08-10 10:01:28 UTC
Version:           1.8.1 (using KDE 3.5.2, Kubuntu Package 4:3.5.2-0ubuntu18.1 dapper)
Compiler:          Target: i486-linux-gnu
OS:                Linux (i686) release 2.6.15-26-386

Sometimes kile suddenly goes wild with 100% CPU. When closing, it crashes:

[KCrash handler]
#6  0x081153e4 in KSelectAction::isShortcutConfigurable ()
#7  0x08143f6b in QTextEdit::setCurrentFont ()
#8  0x081725c7 in QMap<QString, QChar>::insert ()
#9  0x081735f1 in QMap<QString, QChar>::insert ()
#10 0xb6b3aeb9 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#11 0x0816b0f0 in QMap<QString, QChar>::insert ()
#12 0x0816c3db in QMap<QString, QChar>::insert ()
#13 0x0817186d in QMap<QString, QChar>::insert ()
#14 0xb6b3aeb9 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#15 0xb5d071b7 in KateDocument::modStateChanged ()
   from /usr/lib/kde3/libkatepart.so
#16 0xb5d07252 in KateDocument::setModified ()
   from /usr/lib/kde3/libkatepart.so
#17 0xb79aee1d in KParts::ReadWritePart::saveToURL ()
   from /usr/lib/libkparts.so.2
#18 0xb79afd1f in KParts::ReadWritePart::save () from /usr/lib/libkparts.so.2
#19 0xb5d21b02 in KateDocument::save () from /usr/lib/kde3/libkatepart.so
#20 0xb5d0512a in KateView::save () from /usr/lib/kde3/libkatepart.so
#21 0xb5dbd626 in KateView::qt_invoke () from /usr/lib/kde3/libkatepart.so
#22 0xb6b3aeb9 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#23 0xb6b3b954 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#24 0xb745f8a7 in KAction::activated () from /usr/lib/libkdeui.so.4
#25 0xb7495674 in KAction::slotActivated () from /usr/lib/libkdeui.so.4
#26 0xb74b1039 in KAction::qt_invoke () from /usr/lib/libkdeui.so.4
#27 0xb6b3aeb9 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#28 0xb6b3b954 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#29 0xb719c4c5 in KAccelPrivate::menuItemActivated ()
   from /usr/lib/libkdecore.so.4
#30 0xb71d3c08 in KAccelPrivate::emitActivatedSignal ()
   from /usr/lib/libkdecore.so.4
#31 0xb722e9ad in KAccelPrivate::eventFilter () from /usr/lib/libkdecore.so.4
#32 0xb6b38002 in QObject::activate_filters () from /usr/lib/libqt-mt.so.3
#33 0xb6b38080 in QObject::event () from /usr/lib/libqt-mt.so.3
#34 0xb6b755aa in QWidget::event () from /usr/lib/libqt-mt.so.3
#35 0xb6c47762 in QMainWindow::event () from /usr/lib/libqt-mt.so.3
#36 0xb6ad0e56 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#37 0xb6ad11ee in QApplication::notify () from /usr/lib/libqt-mt.so.3
#38 0xb7255d7d in KApplication::notify () from /usr/lib/libkdecore.so.4
#39 0xb71d39cd in KAccelEventHandler::x11Event ()
   from /usr/lib/libkdecore.so.4
#40 0xb725436e in KApplication::x11EventFilter ()
   from /usr/lib/libkdecore.so.4
#41 0xb6a4e457 in qt_set_x11_event_filter () from /usr/lib/libqt-mt.so.3
#42 0xb6a5b74c in QApplication::x11ProcessEvent () from /usr/lib/libqt-mt.so.3
#43 0xb6a754db in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#44 0xb6ae9947 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#45 0xb6ae986a in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#46 0xb6acf965 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#47 0x080f559a in endl ()
#48 0xb636cea2 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#49 0x080756b1 in ?? ()
Comment 1 Thomas Braun 2006-08-11 00:13:59 UTC
Hello,
If you can properly reproduce it, we would be very glad. We know that behaviour already but I have no idea where the culprit lies.
Otherweise I would upgrade to 1.9.1 and see if that fixes your problem.

Thanks
Thomas Braun
Comment 2 Thomas Braun 2009-01-06 22:27:09 UTC
No reply for two years and also a pretty old version.

Therefore closing.

bye,
Thomas

PS: If you disagree feel free to reopen it.