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

[Artem S. Tashkinov]

https://bugs.kde.org/show_bug.cgi?id=176974





--- Comment #66 from Artem S. Tashkinov <t artem mailcity com>  2009-07-17 13:46:58 ---
I'm sorry for flooding but I've just found a number of very good explanations
why libc malloc doesn't return memory to the underlying OS more often than it
does:

http://forums11.itrc.hp.com/service/forums/questionanswer.do?admit=109447626+1247830987898+28353475&threadId=110107
(Subject: Subject: free() not really freeing?)

and

http://www.linuxquestions.org:80/questions/programming-9/how-does-malloc-and-free-functions-work-262165/
(Subject: how does malloc() and free() functions work?)

and comment here:

http://digg.com/software/Firefox_Memory_Leak_Problem_Explored

(starting with "(This is slightly expanded from the comment I made on an older
Firefox memory thread on Digg today.)

The problem for many people is *NOT* a "memory leak". It is a heap memory
fragmentation problem. The following statements apply to Linux systems though I
suspect they may be a consideration under Windows as well. Firefox is built on
top of C++ and C, those use the GNU "libc" ANSI C standard malloc() and free()
to allocate memory.")

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.