From owner-freebsd-questions Fri Mar 1 3:33:16 2002 Delivered-To: freebsd-questions@freebsd.org Received: from smtp-relay1.noc.dsvr.net (virus-1.in.noc.dsvr.net [212.69.192.254]) by hub.freebsd.org (Postfix) with ESMTP id DEC4E37B400 for ; Fri, 1 Mar 2002 03:33:11 -0800 (PST) Received: from [212.69.208.113] (helo=stealthnet.co.uk) by smtp-relay1.noc.dsvr.net with esmtp (Exim 3.34 #1) id 16glHh-0004Un-00 for freebsd-questions@freebsd.org; Fri, 01 Mar 2002 11:33:09 +0000 Received: from JAMES (host213-122-191-220.in-addr.btopenworld.com [213.122.191.220]) by stealthnet.co.uk (8.11.6/8.11.6) with SMTP id g21BX8M29271 for ; Fri, 1 Mar 2002 11:33:08 GMT From: "James Green" To: Subject: RE: out of memory, but there's plenty left! Date: Fri, 1 Mar 2002 11:31:07 -0000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: <20020301035644.E11194-100000@c3po.lpl.arizona.edu> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > I'm running into a problem with my g++ code running out of memory > that might or might not be FreeBSD's fault. The program says, "out of > memory" and dumps core when it gets to about 512MB in size, but there is > plenty of RAM and swap space left. Here is the output from 'top' just > before it crashes: [ snip ] > I am fairly certain that the program is NOT simply running away > and asking for 12GB of RAM at this point in the program because I have > been tweaking it, trying to get it to use less memory and as I have done > so it crashes at later and later points in the program (thus implying an > incremental memory request is sinking the code). I had a new server that I was compiling apache on. It has 256MB of ram, and kept bombing out at different points of compilation with Sig 11s or something. Turned out to be faulty RAM, a very common symptom and problem apparently. Maybe swap the RAM chips for known working ones and see if it resolves the problem? James Green Stealthnet.co.uk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message