Bug 171728 - Process korgac runs after startup at 100% CPU
Summary: Process korgac runs after startup at 100% CPU
Status: RESOLVED UNMAINTAINED
Alias: None
Product: korgac
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-09-27 10:16 UTC by Oliver Zimmermann
Modified: 2013-09-21 21:21 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
kontact bug log (5.79 KB, text/plain)
2008-10-19 18:07 UTC, Sabine
Details
korganizer bug log (3.75 KB, text/plain)
2008-10-19 18:08 UTC, Sabine
Details
Backtracr of Kontact after 100%CPU usage (7.61 KB, application/octet-stream)
2009-01-15 23:23 UTC, Michael Corsa
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Oliver Zimmermann 2008-09-27 10:16:11 UTC
Version:           Unbekannt (using 3.5.10 "release 23.1" , openSUSE )
Compiler:          Target: i586-suse-linux
OS:                Linux (i686) release 2.6.22.18-0.2-default

After the last update korgac runs for a long time at 100% CPU and kontact likewise.
Comment 1 Michael Corsa 2008-10-01 14:12:23 UTC
I am experiencing this same issue.  

I am running openSuSE 11.0, KDE 3.5.10, lastest updates from openSuSE repositories.  Korgac pegs the CPU for minutes before finally starting, but then any changes within the Kontact suite will cause it to hang.  Kopete on startup displays the same issue.  

I reverted back to 3.5.9 version of KDEPIM3 and still had the issue.  

I then further reverted back to versions 3.5.9 on KDEBASE3 and KDELIBS3 and all related dependencies and the issue went away.  I am staying away from any updates to KDE 3.5.10 for the moment.  

Any thoughts or things to try to help analyze would be helpful.
Comment 2 Oliver Zimmermann 2008-10-03 16:55:48 UTC
I would like to revert to 3.5.9 too, but in the repositories available (I use ftp://ftp5.gwdg.de/pub/opensuse/repositories/KDE:/KDE3/openSUSE_10.3/i586) only the last version is available. The SuSE update provides 3.5.7 but I would not want to go back that far. Where to get 3.5.9?
Comment 3 Roman Fietze 2008-10-03 18:47:09 UTC
Additional information:

- When I stop korgac, it exits relatively qickly, but korganzier eats up 100% CPU.

- When I stop korganzier while korgac is still running, korganizer exits relatively quickly, but korgac eats up 100% CPU.

- When I stop korgac whitout korganizer beeing running, koragc also exits relatively quickly.

- Removing std.ics and then starting korganizer does not help, as it probably did about two years ago with a similar error.

- No ToDo's.

Comment 4 Michael Corsa 2008-10-07 20:04:41 UTC
(In reply to comment #2)
> I would like to revert to 3.5.9 too, but in the repositories available (I use
> ftp://ftp5.gwdg.de/pub/opensuse/repositories/KDE:/KDE3/openSUSE_10.3/i586) only
> the last version is available. The SuSE update provides 3.5.7 but I would not
> want to go back that far. Where to get 3.5.9?
> 
I got mine from the repo-oss repository located here: http://download.opensuse.org/distribution/11.0/repo/oss/
Comment 5 Sabine 2008-10-19 18:06:34 UTC
I also have issues with the latest update of Korganizer. Whenever I open Kontact or Korganizer alone I will get the error message that kontact or korgac crashed. I will attach the debug info for both.

I use OpenSUSE 10.3, KDE 3.5.10 release 27.3. Before this latest update I did not experience these crashes. There was an initial spike in CPU activity though. I use the OpenSUSE kde repositories.



Comment 6 Sabine 2008-10-19 18:07:48 UTC
Created attachment 28026 [details]
kontact bug log
Comment 7 Sabine 2008-10-19 18:08:17 UTC
Created attachment 28027 [details]
korganizer bug log
Comment 8 Sabine 2008-10-20 04:32:00 UTC
(In reply to comment #5)
> I also have issues with the latest update of Korganizer. Whenever I open
> Kontact or Korganizer alone I will get the error message that kontact or korgac
> crashed. I will attach the debug info for both.
> 
> I use OpenSUSE 10.3, KDE 3.5.10 release 27.3. Before this latest update I did
> not experience these crashes. There was an initial spike in CPU activity
> though. I use the OpenSUSE kde repositories.
> 

It turned out to be a corrupt ics file. After removing it Korganizer became stable again.
Comment 9 Oliver Zimmermann 2008-10-23 22:55:46 UTC
And which ics-file is it? Can you point me to the location? Thanks!
Comment 10 Roman Fietze 2008-10-25 13:19:29 UTC
Please be careful.

I moved my std.ics away, and started korganizer. Korganizer and korgac both still used 100% CPU for quite some time until they both appeared. Maybe it's just the pure size of a std.ics in combination with the CPU speed that seems to correct the problem. My old 2x500MHz seems to be better suited to detect the slowdown. :)

So I thought it cannot be a corrupt std.ics alone, and I tried to move away ~/.kde/share/apps/korganizer. Still the same effect. Then I did the same with ~/.kde/share/config/koragnizerrc and .../korgacrc in combination with std.ics. Still the same effect.

An strace on korgac (using -p) as soon as korgac wastes CPU while starting shows nothing else than

7148  13:14:30 time(NULL)               = 1224933270
7148  13:14:30 gettimeofday({1224933270, 362405}, NULL) = 0
7148  13:14:30 stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=2309, ...}) = 0
7148  13:14:30 stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=2309, ...}) = 0
7148  13:14:30 stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=2309, ...}) = 0
7148  13:14:30 stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=2309, ...}) = 0
7148  13:14:30 gettimeofday({1224933270, 364728}, NULL) = 0
7148  13:14:30 gettimeofday({1224933270, 364968}, NULL) = 0
7148  13:14:30 gettimeofday({1224933270, 365207}, NULL) = 0
7148  13:14:30 gettimeofday({1224933270, 365446}, NULL) = 0
7148  13:14:30 time(NULL)               = 1224933270
7148  13:14:30 gettimeofday({1224933270, 365965}, NULL) = 0
7148  13:14:30 gettimeofday({1224933270, 366209}, NULL) = 0
7148  13:14:30 gettimeofday({1224933270, 366452}, NULL) = 0
7148  13:14:30 gettimeofday({1224933270, 366695}, NULL) = 0
7148  13:14:30 gettimeofday({1224933270, 366937}, NULL) = 0
7148  13:14:30 time(NULL)               = 1224933270
7148  13:14:30 gettimeofday({1224933270, 367456}, NULL) = 0
7148  13:14:30 stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=2309, ...}) = 0
7148  13:14:30 stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=2309, ...}) = 0
7148  13:14:30 stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=2309, ...}) = 0
7148  13:14:30 stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=2309, ...}) = 0
7148  13:14:30 gettimeofday({1224933270, 369854}, NULL) = 0
7148  13:14:30 gettimeofday({1224933270, 370094}, NULL) = 0
7148  13:14:30 gettimeofday({1224933270, 370336}, NULL) = 0
7148  13:14:30 gettimeofday({1224933270, 370579}, NULL) = 0
7148  13:14:30 time(NULL)               = 1224933270
7148  13:14:30 gettimeofday({1224933270, 371178}, NULL) = 0
7148  13:14:30 gettimeofday({1224933270, 371424}, NULL) = 0
7148  13:14:30 gettimeofday({1224933270, 371666}, NULL) = 0
7148  13:14:30 gettimeofday({1224933270, 371909}, NULL) = 0
7148  13:14:30 gettimeofday({1224933270, 372153}, NULL) = 0
7148  13:14:30 time(NULL)               = 1224933270
7148  13:14:30 gettimeofday({1224933270, 372697}, NULL) = 0
7148  13:14:30 stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=2309, ...}) = 0


while an strace on korganizer show nothing, so there seem to be no system calls at that moment. Huh?
Comment 11 Roman Fietze 2008-11-01 18:37:28 UTC
In the meantime I think it's a more general problem reading e.g. std.vcf or std.ics. So it does not seem to be limited to e.g. korganizer and korgac.

A few minutes ago I wanted to mail an URL that I had opened in konqueror to another person. Neither kontact, korganzier or korgac had been running at that moment. When I clicked "Send link address", a kmail windows opened relatively quickly. But as soon as I started to type the recipients mail adress, kmail started searching my kontact list (kabc's std.vcf). At that moment kmail started to use 100% CPU for quite some time and kmail froze until that reading sucedded, which took about the same time as e.g. starting kadressbook, that also shows that problem.

I also have a second box showing the problem, but because it's an AMD Athlon X2 6400+ it doesn't take that long until kmail, korganizer or korgac come up.

I also tried copying my std.vcf or std.ics to a freshly added user. Same problem. I do not yet know if the problem is caused by a specific entry of those files.
Comment 12 Hugo Costelha 2009-01-07 23:01:51 UTC
I was having the same problem and did the following:
 - I exported my contacts list in csv format;
 - Closed kontact;
 - Deleted all std.vcf* files in $HOME/.kde/share/apps/kabc;
 - Opened kontact again;
 - Imported all my contacts from the csv file exported previously.

I maintained all my contacts this way and haven't experienced the speed problems so far.
Comment 13 Michael Corsa 2009-01-08 02:16:07 UTC
(In reply to comment #12)
> I was having the same problem and did the following:
>  - I exported my contacts list in csv format;
>  - Closed kontact;
>  - Deleted all std.vcf* files in $HOME/.kde/share/apps/kabc;
>  - Opened kontact again;
>  - Imported all my contacts from the csv file exported previously.
> 
> I maintained all my contacts this way and haven't experienced the speed
> problems so far.
> 

Thank you for this.  I just performed the same steps and updated my openSuSE 11.0 from version 3.5.9 to 3.5.10 for PIM and dependencies and now works perfectly.  Thanks for the insight.
Comment 14 Hugo Costelha 2009-01-08 10:05:18 UTC
(In reply to comment #13)
> (In reply to comment #12)
> > I was having the same problem and did the following:
> >  - I exported my contacts list in csv format;
> >  - Closed kontact;
> >  - Deleted all std.vcf* files in $HOME/.kde/share/apps/kabc;
> >  - Opened kontact again;
> >  - Imported all my contacts from the csv file exported previously.
> > 
> > I maintained all my contacts this way and haven't experienced the speed
> > problems so far.
> > 
> 
> Thank you for this.  I just performed the same steps and updated my openSuSE
> 11.0 from version 3.5.9 to 3.5.10 for PIM and dependencies and now works
> perfectly.  Thanks for the insight.
> 

There was probably something that was stored previously, or stored in a different way, which was not properly handled with the more recent versions. Nevertheless, I didn't notice loosing anything during the export/import phase.
Comment 15 Michael Corsa 2009-01-08 22:54:31 UTC
(In reply to comment #14)
> (In reply to comment #13)
> > (In reply to comment #12)
> > > I was having the same problem and did the following:
> > >  - I exported my contacts list in csv format;
> > >  - Closed kontact;
> > >  - Deleted all std.vcf* files in $HOME/.kde/share/apps/kabc;
> > >  - Opened kontact again;
> > >  - Imported all my contacts from the csv file exported previously.
> > > 
> > > I maintained all my contacts this way and haven't experienced the speed
> > > problems so far.
> > > 
> > 
> > Thank you for this.  I just performed the same steps and updated my openSuSE
> > 11.0 from version 3.5.9 to 3.5.10 for PIM and dependencies and now works
> > perfectly.  Thanks for the insight.
> > 
> 
> There was probably something that was stored previously, or stored in a
> different way, which was not properly handled with the more recent versions.
> Nevertheless, I didn't notice loosing anything during the export/import phase.
> 
I did lose some custom field data I had added on the Custom tab, the Field Defs are there, but the data is gone.  Also, pictures assigned are gone, but easily fixed when I have the time.

Thanks again.
Comment 16 Hugo Costelha 2009-01-09 11:41:28 UTC
(In reply to comment #15)
[...]
> I did lose some custom field data I had added on the Custom tab, the Field Defs
> are there, but the data is gone.  Also, pictures assigned are gone, but easily
> fixed when I have the time.
> 
> Thanks again.
> 

All my pics associated to the contacts are retrieved by kopete through MSN and Jabber, that is why I did not loose them, although I had to re-associate the contacts in kopete to the ones in the address book.

It seems that this association with "Sync photo with addressbook" might be the cause for the slowdown. In my case, since I started associating the contacts again with the photo sync option, things have started getting slower again, although not (yet) as slow as before. Will see how it goes in the next days.
Comment 17 Michael Corsa 2009-01-10 17:37:41 UTC
There is definitely something going on with this still.  I had started with a clean Contacts list as I mentioned in my previous comments.  When I did that, I lost the Pictures content that I added to the Misc tab within Contact Maintenance.  Today, I add pictures back in to 45 Contacts, each addition pegged the CPU to over 40% for Kontact and Kopete for up to 2 minutes at a time.

Once I had all the pictures loaded I changed one contact listing in Kopete to use the address link for picture and again both Kontact and Kopete pegged the CPU for 3 minutes.  If I close Kopete and restart it, Kontact and Kopete both peg the CPU for 3 minutes at least and any change to Contacts (anything, just open Maintenance and close it), causes the CPU to peg with Kontact and Kopete.

Not good.  Any suggestions would be welcome.

Running latest KDE3.5.10 version 33.1 under openSuSE 11.0.
Comment 18 Hugo Costelha 2009-01-14 14:43:10 UTC
I can also conclude that this issue is related to the storage of photos associated in the contacts.

The more users I select to have their photo synced between the contacts and their photo in kopete, the slower it gets.

It is now as slow as it was before I had cleaned the contacts.

I wonder if people have the same problem in KDE4?
Comment 19 Hugo Costelha 2009-01-14 19:46:34 UTC
I removed all the photos in my addressbook contacts, removed the option "Sync photo to addressbook" from my contacts in kopete, and the speed is normal again. However, no photos for me now..
Comment 20 Michael Corsa 2009-01-15 01:38:09 UTC
I did the same.  I exported the address book again to a csv file, renamed the original .vcf file which I have not selected as a resource, then imported the csv back in to a new blank vcf file with no photos.  Speed is normal as well.  Something in 3.5.10 caused this slowness to start, somewhere in kdelibs or some component.  For a while I was running the 3.5.9 version of PIM and KDELIBS with all photos intact and this problem did not surface until I updated everything to be the 3.5.10 version.
Comment 21 Sergio Martins 2009-01-15 05:01:47 UTC
Can anyone get a backtrace?

When korgac is at 100%CPU do a kill -s 11 <korgac_pid>

That will make the process crash and give us backtrace, so we can find out where's the problem.

Anyone tried in kde4?
Comment 22 Roman Fietze 2009-01-15 16:59:32 UTC
(In reply to comment #21)

> Can anyone get a backtrace?

If there's no response very soon, I'll do it. With my old 2x500MHz box it's no problem to wait for minutes.

> Anyone tried in kde4?

Yes, I moved to kmail of KDE4 due to that problem, while my desktop and most of the other stuff is still KDE3 of course.

In kmail of KDE4 this does not happen at all, neither the delay when starting kontact, korganizer, korgac not when stopping it. With KDE it even happened when I selected Location->Send Link Adress from within konqueror and started typing a name in the To: field.

Kontact Version 1.3
KMail Version 1.10.3
KAddressBook Version 4.1
Comment 23 Roman Fietze 2009-01-15 17:00:49 UTC
(In reply to comment #21)

Forgot the most important one: KOrganizer Version 4.1.0
Comment 24 Michael Corsa 2009-01-15 23:23:32 UTC
Created attachment 30298 [details]
Backtracr of Kontact after 100%CPU usage

Killed using kill -11.  Hope it helps
Comment 25 Sergio Martins 2009-02-03 02:25:59 UTC
Ok, good to know that this is fixed in KDE4, we can close this then.
Comment 26 Oliver Zimmermann 2009-02-03 08:16:32 UTC
No! We don't close it as KDE 4.2 is far from being as usable as 3.5 was. My "solution" was installing OpenSuSE 11.0 which comes with 3.5.9. and not using any KDE3 repository for updates as these contain the buggy 3.5.10.

I have the impression that it is not really a top priority to eliminate this bug...
Comment 27 Roman Fietze 2009-02-04 07:32:06 UTC
(In reply to comment #25)

> Ok, good to know that this is fixed in KDE4, we can close this then.

Please no. Very many people esp. at work still use 3.5, maybe way more than 95%. And I assume they won't switch to KDE4 before e.g. 4.3 or even 4.4 due to several bugs still in KDE 4, the famous Kicker replacement and the speed of KDE <= 4.2.
Comment 28 Sergio Martins 2009-02-04 18:22:33 UTC
Ok then, but I doubt this is going do be fixed soon. The few existing devs are working on KDE4 bugs.

I would suggest building kdepim3.5 from CVS and start upgrading it until you find the commit responsible for the fix, it doesn't take as long as it sounds, if you have N revisions, try revision N/2, if it works try revision (N/2)/2, if not try (3N/4), in 5 rounds you'll have it narrowed down.
Comment 29 Roman Fietze 2009-02-05 21:01:51 UTC
(In reply to comment #28)

> I would suggest building kdepim3.5 from CVS ...

I think there is a probability above 0 that the bug could also be located in kdelibs/kabc/.

> it doesn't take as long as it sounds

Except if you only have an old 2x500MHz box as I do and probably have to compile and install kdelibs as well. :)

I'll try it, but it'll take some time.
Comment 30 Michael Corsa 2009-02-05 23:52:43 UTC
I don't believe it's in PIM, more likely kdelibs.  When I was trying to troubleshoot to get it to stop dragging my system through the weeds, I had backed dowm the kdepim install from the 3.5.10 version to 3.5.9 and still had the issue.  I also had to install the 3.5.9 version of the kdelibs package which of course then required kdebase3 and a bunch of other dependencies.  I mentioned this in my first post in this thread dated 10/1/2008.  I'm guessing no cares anymore since 4.2 is out, which I'm still not using, tried it, back to 3.5.10.  Right now I'm running on openSuSE 11.1 with KDE 3.5.10 with all the pictures removed from my contacts until/if ever this gets fixed.
Comment 31 Allen Winter 2013-09-21 21:21:29 UTC
the folks dealing with this bug are using 3.5 and that version is no longer supported.

there is no point in keeping the bug open unless it is happening in modern KDE 4.10 or above.
So I will resolve this as unmaintained.

if similar problems are happening in KDE 4.10 or above then feel free to reopen this one or create a new bug.