Bug 325847

Summary:	Akregator consumes 100% cpu and is totally unresponsive
Product:	[Applications] akregator	Reporter:	Shridhar Daithankar <ghodechhap>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	grave
Priority:	NOR
Version:	4.11.2
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	feeds listing that causes problem debug output produced by akregator during problem reproduction backtrace generated from akregator

Description Shridhar Daithankar 2013-10-10 14:56:40 UTC

After a recent upgrade on archlinux, akregator is consuming 100% CPU. Since it was a mass kde upgrade from 4.11.1 to 4.11.2, I cannot confirm exactly which package caused this issue. I suspected akonadi upgrade initially but it does not play any part with akregator it seems(thanks Daniel Vrátil for that information)

I did isolate the isse to my existing feeds. I renamed the feeds.opml and akregator started correctly with default feeds and worked as expected.

However importing back my feeds caused it to freeze totally. It consumes 100% CPU and does not respond to any mouse or keyboard clicks. Menus etc do not work. It had to be killed.

I am attaching feeds.opml for defect reproduction. Also on advise of Daniel Vrátil on the kdepim mailing list, debug output produced by akregator on the command line is also attached. akregator was enabled in kdebugdialog, for this debug output.

Reproducible: Always

Steps to Reproduce:
1. Renamed existing feeds.opml 
2. started akregator. It starts normally.
3. Import original feeds.opml. 
Actual Results:  
akregator freezes. consumes 100% cpu, is totally unresponsive, needs to be killed

Expected Results:  
imported feeds should appear in a separate node in the akregator feeds list. it should continue working as expected.

Comment 1 Shridhar Daithankar 2013-10-10 14:57:50 UTC

Created attachment 82767 [details]
feeds listing that causes problem

This is the opml file which cannot be usably imported in akregator

Comment 2 Shridhar Daithankar 2013-10-10 14:58:34 UTC

Created attachment 82768 [details]
debug output produced by akregator during problem reproduction

Comment 3 Shridhar Daithankar 2013-10-11 02:44:18 UTC

Just a note, even if I have mentioned problem importing feeds, I also faced this post upgrade, where akregator just refused to be usable on startup, when the aforementioned feeds file was my default feeds file.

Its only during debugging I noticed that removing/importing feeds causes sam thing and since thats easier to reproduce for others, I preferred it in the bug report.

Comment 4 Shridhar Daithankar 2013-10-22 04:31:42 UTC

In order to debug this problem further, I removed two feeds(the last two feeds seen before akregator hung) and tried importing that opml.

It resulted in a crash, backtrace is attached.

I have compiled kdepim suite with debug but it seems it always uses libraries from /usr/lib and thus the backtrace is not really useful.

Comment 5 Shridhar Daithankar 2013-10-22 04:32:18 UTC

Created attachment 83005 [details]
backtrace generated from akregator

Comment 6 Denis Kurz 2016-09-24 19:45:25 UTC

This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of akregator (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.

Comment 7 Denis Kurz 2017-01-07 21:57:22 UTC

Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.