Krusader doesn't free memory after closing a viewed file
Bug #451863 reported by
Michał Gołębiowski-Owczarek
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| krusader |
Invalid
|
Medium
|
|||
| krusader (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: krusader
I viewed a 700 MB video file (by pressing F3), closed it and Krusader still occupied 2 GB RAM, which it shouldn't.
(another issue is opening such large files, which I reported as bug #451862)
ProblemType: Bug
Architecture: amd64
CheckboxSubmission: b35340b62900295
CheckboxSystem: d00f84de8a55581
Date: Thu Oct 15 05:20:20 2009
DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Alpha amd64 (20091008)
Package: krusader 1:2.0.0-1ubuntu2
ProcVersionSign
SourcePackage: krusader
Uname: Linux 2.6.31-14-generic x86_64
Revision history for this message
| Michał Gołębiowski-Owczarek (mgol) wrote | #1 |
Revision history for this message
|
|
#2 |
| Changed in krusader: | |
| status: | Unknown → New |
| Changed in krusader: | |
| importance: | Unknown → Medium |
| Changed in krusader: | |
| status: | New → Invalid |
To post a comment you must log in.
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://
This bug has been also reported here: https:/