Bug 177897 - Doesn't free memory from closed tabs
Summary: Doesn't free memory from closed tabs
Status: RESOLVED UNMAINTAINED
Alias: None
Product: akregator
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-12-16 12:50 UTC by Pascal d'Hermilly
Modified: 2017-01-07 22:24 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Pascal d'Hermilly 2008-12-16 12:50:57 UTC 
Version:           1.3.50 (using Devel)
OS:                Linux
Installed from:    Compiled sources

When tabs in akregator are closed, the memomy they consumed is not deallotcated. At least that it the way it looks.
Some test I performed:
Fresh start of akregator with no tabs: 
  memory: 16 M
  shared memomy: 21 M
After opening 4 external webpages with blogs:
  memory: 36 M
  shared memory: 24 M
After closing the 4 tabs:
  memory: 36 M
  shared memory: 25 M

The numbers where found by ksysguard.

It is my impression that akregator should deallocate the 20 MB of used memory and drop back to around 16 MB.
Comment 1 Denis Kurz 2016-09-24 19:45:01 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 2 Denis Kurz 2017-01-07 22:24:51 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.