From owner-freebsd-current@FreeBSD.ORG Fri Apr 25 22:10:20 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DCA2437B401 for ; Fri, 25 Apr 2003 22:10:20 -0700 (PDT) Received: from noisebox.cypherpunks.to (adsl-208-201-229-163.sonic.net [208.201.229.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 51F5943F3F for ; Fri, 25 Apr 2003 22:10:12 -0700 (PDT) (envelope-from shamrock@cypherpunks.to) Received: from VAIO650 (adsl-208-201-229-160.sonic.net [208.201.229.160]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by noisebox.cypherpunks.to (Postfix) with ESMTP id 622E410A; Fri, 25 Apr 2003 22:09:32 -0700 (PDT) From: "Lucky Green" To: Date: Fri, 25 Apr 2003 22:09:15 -0700 Message-ID: <008101c30bb2$0952ee60$6601a8c0@VAIO650> 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, Build 10.0.2627 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Importance: Normal Subject: Re: Hang after running out of memory X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Apr 2003 05:10:21 -0000 On Apr 20, "Craig Reyenga" wrote: > I have been following the thread here on current@ about problems > occuring when running out of memory, so I wrote a C++ program that > simply mallocs about 144M of memory. My system has 256MB+491MB(swap). > I can run the system out of memory just fine by running multiple > copies of the program, and the kernel does kill one if I run too many, > however shortly after, when I go to killall the programs the system > hangs, (although pings, etc manage to survive for a few mintues > longer) and I have no choice but to press the reset button. While it > is hung, I _can_ press ^T and it shows the load, which increases by 1 > about every 45 seconds: I have seen twice what I believe may be a similar problem: when logged in via ssh (puTTY), the terminal stops responding to commands. Unlike with an interrupted ssh connection, in which no characters are echoed, in this puTTY echoed ^C and ^Z literally to the screen. At that point, FreeBSD stops accepting SSH connections, though the machine continues to respond to pings. In each case, the server showed high loads due to GBDE and low memory, for so far unknown reasons (perhaps GBDE), just before the error occurred. Both time this happened, the server would again accept connections after about 30 min. There were no disk errors in the logs. --Lucky