Bug 329720 - Akregator memory leak?
Summary: Akregator memory leak?
Status: RESOLVED UNMAINTAINED
Alias: None
Product: akregator
Classification: Applications
Component: general (show other bugs)
Version: 4.12
Platform: Ubuntu Linux
: NOR normal (vote)
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-01-08 13:25 UTC by Thomas Tanghus
Modified: 2018-02-01 09:47 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Tanghus 2014-01-08 13:25:27 UTC
After having Akregator open for a couple of days it's resident memory use goes from ~400MB to >2500MB.
I run it standalone and have around 150 feeds.

Reproducible: Always

Steps to Reproduce:
1. Start Akregator 
2. Watch memory usage via System Activity or the RES column in top/htop
3. Let it run for a couple of days
4. Repeat step 2.
Actual Results:  
The memory usage is over 5 times what it was when starting the program

Expected Results:  
The memory usage shouldn't have increased significantly.
Comment 1 Frank Osterfeld 2014-04-25 17:22:14 UTC
Akregator reads the item data on first access and then keeps them in memory until exit. That's known so far. If it grows in memory beyond that, that'd be a leak.
Comment 2 Thomas Tanghus 2014-04-25 17:49:28 UTC
Anything I should do to debug it? It should be quite reproducable for others as well though. Just checked and it's currently consuming 1.4GB and has run since last crash some time yesterday.
Comment 3 Alad Wenter 2015-01-03 13:03:51 UTC
I can confirm this issue using akregator 4.14.3 under Qt 4.8.6-4 and Arch Linux
Comment 4 Denis Kurz 2017-06-23 20:01:29 UTC
This bug has never been confirmed for a KDE PIM version that is based on KDE Frameworks (5.x). Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the oportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it.

Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.
Comment 5 Denis Kurz 2018-02-01 09:47:02 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12; preferably much more recent), please open a new one unless it already exists. Thank you for all your input.