Bug 210630 - Krusader doesn't free memory after closing a viewed file
Summary: Krusader doesn't free memory after closing a viewed file
Status: RESOLVED WORKSFORME
Alias: None
Product: krusader
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Shie Erlich
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-15 05:29 UTC by Michał Z. Gołębiowski
Modified: 2012-11-07 01:02 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 Michał Z. Gołębiowski 2009-10-15 05:29:42 UTC 
Version:           2.0.0-1ubuntu2 (using KDE 4.3.2)
Compiler:          gcc/g++ 4.4.1-1ubuntu2 
OS:                Linux
Installed from:    Ubuntu Packages

I viewed a 700 MB video file (by pressing F3), closed it and Krusader still occupied 2 GB RAM, which it shouldn't.

See also http://bugs.kde.org/show_bug.cgi?id=210629.

This bug has been also reported here: https://bugs.launchpad.net/ubuntu/+source/krusader/+bug/451863
Comment 1 Jekyll Wu 2012-11-07 01:02:29 UTC 
Can't reproduce it using 2.4.0-beta3. Feel free to reopen if the problem still exists in recent version.