Version: (using KDE KDE 3.5.4) Installed from: Ubuntu Packages Compiler: gcc4.0.3 (from Ubuntu Dapper Drake) OS: Linux Attention: This bug might be an duplicate of Bug #107921, but i'm not able to decide this. System: AMD Athlon XP 2400+ 256 MB RAM KDE 3.5.4 Konsole 1.6.4 Kubuntu 6.06 (Dapper Drake) Konsole Settings: 10000 lines history Colour scheme white on black Font DejaVu Sans Mono Normal 9 Im using Konsole to test multiple devices in the network at the same time. So i usually open between 4 and 9 Konsole windows (on one Desktop, one for each device to test) and in each Window up to 6 sessions - one for each test, they are all running at the same time. While running the tests (per ssh, snmp and some self programmed applications) the Konsole consumes more and more memory. The system has 256 MB so after around 10 hours you can see the system is beginning to use the swap more and more. If i close all Konsole windows (this may be a hard job to do if the system is swapping :-() the memory will released completely, without a restart necessary. This is not happening just leaving the System alone for this time or just having another application open (f.e. Konqueror or Kontact). But since the application don't do anything in this time (while the console continously prints out logs and results of the test and starts other test automatically) it might be that this is not a Konsole specific problem. This problem does not exist (or is much smaller - so i'm not able to reproduce it here) in KDE 3.5.3 (on Kubuntu 5.10, Konsole 1.6.2) running on the same hardware.
*** Bug 135136 has been marked as a duplicate of this bug. ***
*** Bug 135137 has been marked as a duplicate of this bug. ***
*** Bug 135138 has been marked as a duplicate of this bug. ***
Hello, Is this problem still present? If so, please post the output of /proc/<process id of konsole>/status after it has been running for an extended period of time. (the process ID can be obtained by running 'ps -C konsole')
Closing bug as there has not been a response to my earlier comments. Please re-open if problem still exists with current versions of KDE.