This is the mail archive of the glibc-bugs@sources.redhat.com mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug libc/167] malloc() eats excess ram


------- Additional Comments From bluefoxicy at linux dot net  2004-05-16 20:52 -------
Sorry, I meant to say

--
This raises one problem that can be manifested in two ways.  The less extreme
problem is seen above:  There is unused, but allocated ram.  The more extreme
problem is best illustrated with a new example.
--

Instead

--
This raises one problem that can be manifested in two ways.  The less extreme
problem is seen above:  There are intermittent segments of unused, but allocated
ram.  The more extreme problem is best illustrated with a new example, and is
simply a large scale manifestation of unused, allocated ram.
--

Sorry :)

-- 


http://sources.redhat.com/bugzilla/show_bug.cgi?id=167

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]