Re: akregator uses 100% cpu with akonadi upgrade

Am Freitag, 11. Oktober 2013, 08:14:27 schrieb Shridhar Daithankar:
> On Thursday, October 10, 2013 05:19:24 PM Martin Steigerwald wrote:
> > Am Donnerstag, 10. Oktober 2013, 20:29:27 schrieb Shridhar Daithankar:
> > > done. https://bugs.kde.org/show_bug.cgi?id=325847
> > 
> > There is a known issue when after unsafe shutdown of Akregator a feed list
> > file (I think its opml files) is broken. There already is a bug report
> > about that.
> > 
> > You may want to try with a backup of those files.
> > 
> > However I didn´t see this bug since a long time and I had quite some
> > unsafe
> > shutdowns :)
> > 
> > Hmmm, I think it was:
> > 
> > https://bugs.kde.org/show_bug.cgi?id=116482
> > 
> > but thats a crash. So maybe you have a different issue.
> 
> I am for sure not facing problem with unclean shutdown of akregator. Since
> it becomes totally unresponsive, I have to kill it every time. And it
> starts fine next time, asking for restoring session.

You tell its a problem with the feeds.

Well, I think it would be beneficial to know with which feed.

I know… but without knowing that.

Maybe it can help to attach a strace to Akregator *before* it becomes 
unresponsive.

strace -fF -p PID -e file

or "-e open" or simply start it with

strace -fF -e file akregator

You can redirect output of strace with "-o" option.

In that way you might find out with which feed file Akregator is busy with when 
it becomes unresponsive.

Ciao,
-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7
_______________________________________________
KDE PIM users mailing list
Subscription management: https://mail.kde.org/mailman/listinfo/kdepim-users