From owner-freebsd-bugs@FreeBSD.ORG Thu May 5 09:20:06 2005 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0C83016A4CE for ; Thu, 5 May 2005 09:20:06 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id EBB2543DBA for ; Thu, 5 May 2005 09:20:05 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j459K5ME082020 for ; Thu, 5 May 2005 09:20:05 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j459K4c1082019; Thu, 5 May 2005 09:20:04 GMT (envelope-from gnats) Date: Thu, 5 May 2005 09:20:04 GMT Message-Id: <200505050920.j459K4c1082019@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Bruce Evans Subject: Re: kern/80626: Out of memory ? then dead X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Bruce Evans List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 May 2005 09:20:06 -0000 The following reply was made to PR kern/80626; it has been noted by GNATS. From: Bruce Evans To: Giorgos Keramidas Cc: freebsd-gnats-submit@freebsd.org Subject: Re: kern/80626: Out of memory ? then dead Date: Thu, 5 May 2005 19:14:06 +1000 (EST) On Wed, 4 May 2005, Giorgos Keramidas wrote: > On 2005-05-04 18:48, Nie Baopeng wrote: > > I use FluxBox Wm , sometimes the all GUI is Dead , any keys can't been > > used other than the Ctrl+Alt+Del ,even can't change to console . I see > > the log . The end of the line write that Xorg OUt Of Mamory . > > > I have No Swap yeah, and have 512 real mem . I known if use swap can > > slove this , but is not a poblem ? > > This is not really a bug. Completely filling up all the physiucal > memory when there is no swap space available is known to cause hangs. It shouldn't cause any different behaviour that filling up all of physical and virtual memory when there is some swap space available. The kernel should start killing processes and not hang, but applications might not like this and children of the killed processes might hang. Bruce