From owner-freebsd-current Fri Jan 3 06:20:17 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id GAA23296 for current-outgoing; Fri, 3 Jan 1997 06:20:17 -0800 (PST) Received: from deepcore.cybercity.dk (ravenock.cybercity.dk [194.16.57.32]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id GAA23290 for ; Fri, 3 Jan 1997 06:20:06 -0800 (PST) Received: (from sos@localhost) by deepcore.cybercity.dk (8.8.4/8.7.3) id PAA07022; Fri, 3 Jan 1997 15:20:35 +0100 (MET) Message-Id: <199701031420.PAA07022@deepcore.cybercity.dk> Subject: Re: Swap leak in -current? To: grog@lemis.de Date: Fri, 3 Jan 1997 15:20:32 +0100 (MET) Cc: FreeBSD-current@FreeBSD.ORG In-Reply-To: <199701031349.OAA15162@freebie.lemis.de> from "grog@lemis.de" at "Jan 3, 97 02:49:28 pm" From: sos@FreeBSD.ORG Reply-to: sos@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL15 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In reply to grog@lemis.de who wrote: > I've just failed a 'make world' for the second time after running out > of swap space. I don't understand why: it looks like the make process > is using up swap at a ridiculous rate. Here's the scenario: Pentium > 133 with 64 MB of memory, a hungry X server using about a third of > this, two swap spaces with a total of 150 MB. WoW! I just posted a message on cvs checkout dying the same horrible death (actually it is co that dies)... Anybody played with the malloc code resently, it seems free fails :(... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end ..