From owner-freebsd-hackers Sat Jul 22 8: 2:14 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 420C237B5C5 for ; Sat, 22 Jul 2000 08:02:10 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p15-dn02kiryunisiki.gunma.ocn.ne.jp [211.0.245.80]) by peach.ocn.ne.jp (8.9.1a/OCN/) with ESMTP id AAA02730; Sun, 23 Jul 2000 00:01:59 +0900 (JST) Message-ID: <3979B777.A8AD8511@newsguy.com> Date: Sun, 23 Jul 2000 00:02:15 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Mario Sergio Fujikawa Ferreira Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: sysutils/memtest and FreeBSD References: <20000721175757.B319@Fedaykin.here> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mario Sergio Fujikawa Ferreira wrote: > > Backtracing showed that the problem was due > to the malloc function inside the get_mem function. > get_mem() is used to find out the largest possible memory segment. > It incrementaly reduces the segment passed to malloc to alloc. > It is the malloc function allright. It core dumps on the > 1st pass on get_mem(), there is no time to do_reduce. Very weird. ;( Because FreeBSD overcommits, malloc() will only fail in case of artificial limits being reached (like those of login.conf). If FreeBSD suddenly finds itself in a position of not being able to meet the previous commitments wrt to memory allocation, it will kill the application with the largest memory allocations. I'll bet you the fifth season of Babylon 5 this is what's happening. :-) Try limiting the maximum memory allocation to the total physical RAM. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@white.bunnies.bsdconspiracy.net Satan was once an angel, Gates started by writing a BASIC interpreter. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message