Bug 127069

Summary:	new calendar entry in kontact causes high cpu load
Product:	[Applications] korganizer	Reporter:	Christian Patsch <christian>
Component:	general	Assignee:	Daniel Molkentin <molkentin>
Status:	RESOLVED DUPLICATE
Severity:	normal
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Debian testing
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Christian Patsch 2006-05-10 12:05:43 UTC

Version:           1.2 (using KDE KDE 3.5.2)
Installed from:    Debian testing/unstable Packages

Every Time I create a new calendar entry in Kontact - by double-clicking in the day view - , the kontact process rises the cpu load to 70 % at a minimum. After some seconds, the new calendar entry window appears. I can edit the data in a normal way, saving the entry again causes a very high cpu load by the kontact process.

The Calendar is saved on the local harddisk in the file /home/$USER/.kde/share/apps/korganizer/std.ics .

Maybe there is an option to track down, but I'm not aware of it at the moment. Any help on this would be highly appreciated.

Comment 1 Bram Schoenmakers 2006-05-11 16:20:05 UTC

Is there any useful output when you run KOrganizer from the command line?

Comment 2 Ulrich Gemkow 2006-05-15 23:09:18 UTC

we also see this problem. Sometimes a crash follows the long pauses,
a crash report is appended. Maybe this helps...

Using host libthread_db library "/lib/tls/libthread_db.so.1".
`shared object read from target memory' has disappeared; keeping its symbols.
[Thread debugging using libthread_db enabled]
[New Thread -1240783168 (LWP 3405)]
[New Thread -1280185424 (LWP 3411)]
[Thread debugging using libthread_db enabled]
[New Thread -1240783168 (LWP 3405)]
[New Thread -1280185424 (LWP 3411)]
[Thread debugging using libthread_db enabled]
[New Thread -1240783168 (LWP 3405)]
[New Thread -1280185424 (LWP 3411)]
[New Thread -1271792720 (LWP 3410)]
[New Thread -1263400016 (LWP 3409)]
[New Thread -1255007312 (LWP 3408)]
[KCrash handler]
#6  0xb687b349 in QBoxLayout::setupGeom ()
   from /usr/local/kde35/qt/lib/libqt-mt.so.3
#7  0xb687bf31 in QBoxLayout::minimumSize ()
   from /usr/local/kde35/qt/lib/libqt-mt.so.3
#8  0xb68351ca in QLayout::totalMinimumSize ()
   from /usr/local/kde35/qt/lib/libqt-mt.so.3
#9  0xb6881ff2 in qSmartMinSize () from /usr/local/kde35/qt/lib/libqt-mt.so.3
#10 0xb683477a in QWidgetItem::minimumSize ()
   from /usr/local/kde35/qt/lib/libqt-mt.so.3
#11 0xb687ae7d in QBoxLayout::setupGeom ()
   from /usr/local/kde35/qt/lib/libqt-mt.so.3
#12 0xb687bf99 in QBoxLayout::sizeHint ()
   from /usr/local/kde35/qt/lib/libqt-mt.so.3
#13 0xb683525f in QLayout::totalSizeHint ()
   from /usr/local/kde35/qt/lib/libqt-mt.so.3
#14 0xb68c4b48 in QWidget::sizeHint ()
   from /usr/local/kde35/qt/lib/libqt-mt.so.3
#15 0xb693c544 in QFrame::sizeHint ()
   from /usr/local/kde35/qt/lib/libqt-mt.so.3
#16 0xb69c0711 in QWidgetStack::sizeHint ()
   from /usr/local/kde35/qt/lib/libqt-mt.so.3
#17 0xb69ad8af in QTabWidget::sizeHint ()
   from /usr/local/kde35/qt/lib/libqt-mt.so.3
#18 0xb712efb4 in KJanusWidget::minimumSizeHint ()
   from /usr/local/kde35/lib/libkdeui.so.4
#19 0xb712c1a8 in KDialogBase::minimumSizeHint ()
   from /usr/local/kde35/lib/libkdeui.so.4
#20 0xb712be07 in KDialogBase::sizeHint ()
   from /usr/local/kde35/lib/libkdeui.so.4
#21 0xb712bdcc in KDialogBase::adjustSize ()
   from /usr/local/kde35/lib/libkdeui.so.4
#22 0xb6a03820 in QDialog::show () from /usr/local/kde35/qt/lib/libqt-mt.so.3
#23 0xb310d578 in CalendarView::newEvent (this=0x84e93e0, 
    fromHint=@0xbfa71ad0, toHint=@0xbfa71ab8, allDay=false)
    at calendarview.cpp:996
#24 0xb310d179 in CalendarView::newEvent (this=0x84e93e0)
    at calendarview.cpp:940
#25 0xb3114107 in CalendarView::qt_invoke (this=0x84e93e0, _id=62, 
    _o=0xbfa71be0) at calendarview.moc:970
#26 0xb6896410 in QObject::activate_signal ()
   from /usr/local/kde35/qt/lib/libqt-mt.so.3
#27 0xb6896a81 in QObject::activate_signal ()
   from /usr/local/kde35/qt/lib/libqt-mt.so.3
#28 0xb70eedb4 in KAction::activated ()
   from /usr/local/kde35/lib/libkdeui.so.4
#29 0xb718e1d9 in KAction::slotActivated ()
   from /usr/local/kde35/lib/libkdeui.so.4
#30 0xb71f3b62 in KAction::slotPopupActivated ()
   from /usr/local/kde35/lib/libkdeui.so.4
#31 0xb71f3bf9 in KAction::qt_invoke ()
   from /usr/local/kde35/lib/libkdeui.so.4
#32 0xb6896410 in QObject::activate_signal ()
   from /usr/local/kde35/qt/lib/libqt-mt.so.3
#33 0xb6b908b7 in QSignal::signal ()
   from /usr/local/kde35/qt/lib/libqt-mt.so.3
#34 0xb68ad41e in QSignal::activate ()
   from /usr/local/kde35/qt/lib/libqt-mt.so.3
#35 0xb698c9af in QPopupMenu::mouseReleaseEvent ()
   from /usr/local/kde35/qt/lib/libqt-mt.so.3
#36 0xb70ea412 in KPopupMenu::mouseReleaseEvent ()
   from /usr/local/kde35/lib/libkdeui.so.4
#37 0xb68c8dc7 in QWidget::event () from /usr/local/kde35/qt/lib/libqt-mt.so.3
#38 0xb683b3f9 in QApplication::internalNotify ()
   from /usr/local/kde35/qt/lib/libqt-mt.so.3
#39 0xb683b639 in QApplication::notify ()
   from /usr/local/kde35/qt/lib/libqt-mt.so.3
#40 0xb6ef6dfc in KApplication::notify ()
   from /usr/local/kde35/lib/libkdecore.so.4
#41 0xb67def62 in QETWidget::translateMouseEvent ()
   from /usr/local/kde35/qt/lib/libqt-mt.so.3
#42 0xb67dd29f in QApplication::x11ProcessEvent ()
   from /usr/local/kde35/qt/lib/libqt-mt.so.3
#43 0xb67eec78 in QEventLoop::processEvents ()
   from /usr/local/kde35/qt/lib/libqt-mt.so.3
#44 0xb684f5ff in QEventLoop::enterLoop ()
   from /usr/local/kde35/qt/lib/libqt-mt.so.3
#45 0xb684f55c in QEventLoop::exec ()
   from /usr/local/kde35/qt/lib/libqt-mt.so.3
#46 0xb683a73c in QApplication::exec ()
   from /usr/local/kde35/qt/lib/libqt-mt.so.3
#47 0x0805b491 in main (argc=1, argv=0xbfa72ac4) at main.cpp:177

Comment 3 Allen Winter 2006-09-12 05:00:06 UTC

Does this still happen with KOrganizer in KDE 3.5.4?

I know we fixed one pretty bad performance bug in that version.

Comment 4 Bram Schoenmakers 2006-10-28 15:35:49 UTC


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