Bug 184925 - Akregator leaking memory when fetching all feeds
Summary: Akregator leaking memory when fetching all feeds
Status: RESOLVED FIXED
Alias: None
Product: akregator
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-19 12:05 UTC by Toke Høiland-Jørgensen
Modified: 2009-04-16 22:59 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Toke Høiland-Jørgensen 2009-02-19 12:05:48 UTC 
Version:           1.4.0 (using KDE 4.2.0)
Compiler:          GCC 4.1.2 
OS:                Linux
Installed from:    Gentoo Packages

Long-running Akregator processes end up consuming gigabytes of memory, slowing the whole system to a crawl. It would appear that there is a memory leak when fetching all feeds.

How to reproduce:

- Open Akregator with several feeds
- Watch the process' memory usage in 'top' or similar utility
- Click "Fetch all feeds"
- Memory usage increases by (in my case) several megabytes.

The increase in memory usage is consistant each time the "fetch all feeds" button is clicked, and appearantly also for automatic feed updates.
Comment 1 Frank Osterfeld 2009-02-19 12:17:24 UTC 
I fixed a memleak in libsyndication leaking feed data for RSS 1.0 (i.e. RDF) feeds. (in trunk, atm). It still needs investigation if this fixes the issue completely.
Comment 2 Toke Høiland-Jørgensen 2009-02-21 14:48:29 UTC 
Will this be backported to the 4.2 branch? I would test it in trunk, but I don't have a KDE build environment setup, and unfortunately doesn't have the time to look into it for the time being...
Comment 3 Toke Høiland-Jørgensen 2009-04-16 00:44:40 UTC 
I've had the 4.2.1 version of Akregator running for several days (even weeks) now without seeing a memory leak.
Comment 4 Frank Osterfeld 2009-04-16 22:59:46 UTC 
Thanks for the feedback - I consider it fixed then and close.