[Bug 295532] New: Akonadi hogs cpu when updating remote ics feed from google

[Daniel Faust]

https://bugs.kde.org/show_bug.cgi?id=295532

            Bug ID: 295532
          Severity: normal
           Version: 4.8
          Priority: NOR
          Assignee: kdepim-bugs at kde.org
           Summary: Akonadi hogs cpu when updating remote ics feed from
                    google
    Classification: Unclassified
                OS: Linux
          Reporter: hessijames at gmail.com
          Hardware: openSUSE RPMs
            Status: NEW
         Component: ICal file resource
           Product: Akonadi

Created attachment 69374
  --> https://bugs.kde.org/attachment.cgi?id=69374&action=edit
A copy of the ics feed in case it gets changed

I am using a remote ics feed from google since KDE 4.7.
After upgrading to KDE 4.8.1 akonadi will hog the cpu when I enable periodic
updates for that ics file. Disabling the periodic updates again won't change
anything. Only removing the calendar stops the cpu usage. After that I can add
a new calendar with the same ics file without any problem as long as I don't
enable periodic updates.
The ics feed creating this problem is:
https://www.google.com/calendar/ical/i2atv0kpsvau8npuhugfn8f6ho@group.calendar.google.com/public/basic.ics

The cpu usage starts with a delay after enabling periodic updates and on the
console I executed 'akonadictl start' I get an uncountable amount of these
messages:
AkonadiAgentServer(1965)/akonadiserializer (calendar)
Akonadi::SerializerPluginKCalCore::deserialize: Failed to parse incidence! Item
id =  9088 Storage collection id  67 parentCollectionId =  -43235 
AkonadiAgentServer(1965)/akonadiserializer (calendar)
Akonadi::SerializerPluginKCalCore::deserialize: "" 
AkonadiAgentServer(1965)/libakonadi Akonadi::ItemSerializer::deserialize:
Unable to deserialize payload part: "RFC822" 
AkonadiAgentServer(1965)/libakonadi Akonadi::ItemSerializer::deserialize:
Payload data was:  "" 

During that the akonadi systemsettings control module shows that the status of
the calendar resource causing this problem is switching between reconnecting
and ready all the time.

All other (remote ics) calendars like http://www.kde.org/releaseschedule.ics
work fine.

-- 
You are receiving this mail because:
You are the assignee for the bug.