Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.ecn.uoknor.edu!feed1.news.erols.com!howland.erols.net!news.nacamar.de!fu-berlin.de!irz401!orion.sax.de!uriah.heep!news From: j@uriah.heep.sax.de (J Wunsch) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: Memory problems FreeBSD 2.1.6 Date: 28 Nov 1996 23:47:25 GMT Organization: Private BSD site, Dresden Lines: 20 Message-ID: <57l8ad$hr0@uriah.heep.sax.de> References: <01bbdcbf$36ed3480$1782099a@taco> Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) NNTP-Posting-Host: localhost.heep.sax.de Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: knews 0.9.6 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E "Taco Scargo" <taco@webguide.net> wrote: > The problem I am really worried about is the fact that the OS caches all > files that have been opened and does NOT release the memory when system > memory is getting low. Of course, it does! What you're seeing is probably that your BSDi application uses the `classic' BSD malloc (statically linked), which was a known sucker wrt. its VM consumption. There's not much you can do here (short of asking the vendor to re-link it against a better malloc), except of adding more swap space. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)