From owner-freebsd-stable@FreeBSD.ORG Mon Aug 11 01:44:39 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8BDC937B401 for ; Mon, 11 Aug 2003 01:44:39 -0700 (PDT) Received: from anholt.dyndns.org (12-224-152-126.client.attbi.com [12.224.152.126]) by mx1.FreeBSD.org (Postfix) with ESMTP id F166543F85 for ; Mon, 11 Aug 2003 01:44:38 -0700 (PDT) (envelope-from eta@lclark.edu) Received: from anholt.dyndns.org (localhost [127.0.0.1]) by anholt.dyndns.org (8.12.9/8.12.9) with ESMTP id h7B8iYp8012327; Mon, 11 Aug 2003 01:44:35 -0700 (PDT) (envelope-from eta@lclark.edu) Received: (from anholt@localhost) by anholt.dyndns.org (8.12.9/8.12.9/Submit) id h7B8iUjs012326; Mon, 11 Aug 2003 01:44:30 -0700 (PDT) X-Authentication-Warning: anholt.dyndns.org: anholt set sender to eta@lclark.edu using -f From: Eric Anholt To: Daniel C Bastos In-Reply-To: <20030811042149.1175eca5.daniel@slashlog.org> References: <20030811042149.1175eca5.daniel@slashlog.org> Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <1060591468.12253.5.camel@leguin> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.4 Date: Mon, 11 Aug 2003 01:44:29 -0700 cc: freebsd-stable@freebsd.org Subject: Re: swap_pager: out of swap space X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Aug 2003 08:44:39 -0000 On Mon, 2003-08-11 at 01:21, Daniel C Bastos wrote: > Aug 11 03:56:34 danux /kernel: swap_pager: out of swap space > Aug 11 04:02:34 danux /kernel: swap_pager_getswapspace: failed > Aug 11 04:02:34 danux /kernel: pid 278 (XFree86), uid 0, was killed: out > of swap space > > i was actually looking at the screen and then everything stopped (mouse > etc). i could not switch to console, but a ctrl+alt+del rebooted fine. > > one thing that could be taking a lot of memory was a program called > "xwatch" (/usr/ports/sysutils/xwatch) reading a log file (with a lot of > activity from a software i'm developing) and xwatch might not be > limiting its buffer... ? i don't know, wouldnt the kernel kill xwatch > instead of xfree86? > > i appreciate any info on this. thanks. Pixmaps allocated by X clients are actually allocated by the server. If xwatch leaked that memory, or just allocated enough of it, it could cause XFree86 to be chosen by the OOM killer. -- Eric Anholt eta@lclark.edu http://people.freebsd.org/~anholt/ anholt@FreeBSD.org