Summary: | Changing the day to show uses 100% cpu | ||
---|---|---|---|
Product: | [Applications] kontact | Reporter: | Søren Holm <sgh> |
Component: | calendar | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | smartins |
Priority: | NOR | ||
Version: | 4.5 pre | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: | korganizerrc that makes my cpu go wild when changing date |
Description
Søren Holm
2010-07-03 00:27:46 UTC
This still occurs in KDE SC 4.5.0 rc2 Can someone please verify and confirm. It renders korganizer unusable to browse past and future months. How many events do you have? Wich calendar type? Ics file? Wich view are you in? Day, work, month? (day i suppose) After deleting korganizerrc the behavior stopped .... I should have saved the file so we could see what caused it. Thanks for the reply anyway. Created attachment 49698 [details]
korganizerrc that makes my cpu go wild when changing date
I think this bug should be reopened. Deleting korganizerrc is a workaround, but users upgrading from 4.4.x will experience this problem. Can you answer comment #2 ? Sergio: Removing all calendars does not resolve it, so I am guessing that is nothing to do with the actual content of the calendar. I found out what is wrong. Setting the holyday region to something else than "none" triggers the high cpu usage when changing date. SVN commit 1157649 by smartins: Call HolidayRegion::holidays( start, end ) once, instead of calling HolidayRegion::holdays( date ) 42 times. Saves almost 2 seconds when using the date navigator. BUG: 243472 M +4 -1 kodaymatrix.cpp M +24 -6 koglobals.cpp M +10 -0 koglobals.h WebSVN link: http://websvn.kde.org/?view=rev&revision=1157649 Sweet :D |