[Konsole-devel] [Bug 176974] High memory consumption when using Konsole for a longer time.

Michael Meier mick22 at gmx.at
Fri Jun 12 17:09:18 UTC 2009


--- Comment #44 from Michael Meier <mick22 gmx at>  2009-06-12 19:09:13 ---
I discovered a problem with copy&paste from the history in the current patch. I
am working on resolving that.

As for the mem leak: I am not sure one exists. Valgrind shows some lost blocks,
but they seem all related to QT's font classes. I can't find anything in the
history code or in konsole itself.

The reason for VmData not shrinking (most of the time) upon mem being freed by
"free" or "delete" is IMHO not caused by anything in the konsole code but
rather is a normal consequence of heap fragmentation. And as I described in my
last post, this can be observed in other applications, too.

If you are lucky enough to free the last block allocated on the heap, the
system might be able to return everything until the end of the but-last block.
Otherwise, nothing can be freed as this would require heap compaction. At least
this is the case with small blocks in the brk() area. Large blocks are usually
allcated using mmap and could be freed independently, but for the history
that's not really useful, unless you want to use mallopt() and implement some
sort of customized allocation and partitioned heap.

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 mailing list