Date: Mon, 12 Jul 1999 09:30:53 +0900 From: "Daniel C. Sobral" <dcs@newsguy.com> To: Jon Ribbens <jon@oaktree.co.uk> Cc: freebsd-hackers@FreeBSD.ORG, tech-userlevel@netbsd.org, tech@openbsd.org Subject: Re: Replacement for grep(1) (part 2) Message-ID: <3789373D.9B1811F3@newsguy.com> References: <Pine.GSO.4.10.9907052110250.13873-100000@uther.wam.umd.edu> <xzp7locthir.fsf@flood.ping.uio.no> <xzp1zektgp2.fsf@flood.ping.uio.no> <5laet8b2l8.fsf@assaris.sics.se> <xzpiu7wrx7q.fsf@flood.ping.uio.no> <5lemij265u.fsf@assaris.sics.se> <3788714D.4E666FFA@newsguy.com> <19990712002043.C7067@oaktree.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
Jon Ribbens wrote: > > "Daniel C. Sobral" <dcs@newsguy.com> wrote: > > OTOH, though, FreeBSD's malloc() is very unlikely to return an out > > of memory error. > > Why is that? Because memory (as in *real* memory, either RAM or swap) is allocated on-demand. So you can allocate any amount of virtual memory that the system can possibly provide you, even though you'll run out of memory much earlier, because other resources are also consuming it. > What happens if the process hits its resource limits? If the system runs out of memory, the biggest process is killed. It might or might not be the one demanding additional memory. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org I'm one of those bad things that happen to good people. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3789373D.9B1811F3>