[Konsole-devel] [Bug 176974] High memory consumption when using Konsole for a longer time.
Artem S. Tashkinov
t.artem at mailcity.com
Mon Jun 8 07:17:08 UTC 2009
--- Comment #16 from Artem S. Tashkinov <t artem mailcity com> 2009-06-08 09:17:04 ---
(In reply to comment #12)
> > I can see that at least in the source the problem is acknowledged
> > and marked as critical
> Those comments were written back in the KDE 3 days and I believe do not refer
> to a leak but just that if you set the number of scrollback lines to a very
> large number, open many tabs and fill all those buffers then a lot of memory
> will be used - see my calculations above.
> > Is it possible that (1) is just a simple bug caused by a
> > missing destructor, missing delete or similar?
> I need to confirm that there is actually a leak first - not just a lot of
> memory being used as a result of many tabs and a large scrollback buffer in
> each. I valgrinded a simple Konsole session with 1K scrollback opening tabs,
> filling the scrollback buffer and then closing the tab but did not see any
> relevant problems in the leak report.
> It would be helpful if you could try as well using:
> valgrind --leak-check=full --show-reachable=yes konsole --nofork
Robert, definitely there's a memory leak, since I've already indicated that
after closing all bash sessions in Konsole doesn't reduce Konsole's memory
As a simple experiment, open an empty Konsole, set history Konsole's history
scollback value to 30 thousands lines, observe its RSS value (15M in my case).
Then open 10 bash sessions, cat 50K lines file in each of them, then open a new
bash session and close 10 'old' bash sessions. Something tells me that RSS
value of Konsole process should be restored.
In my case I see 664MB of memory STILL occupied by Konsole. That's insane.
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the konsole-devel