From owner-freebsd-current@FreeBSD.ORG Mon Oct 30 23:06:52 2006 Return-Path: X-Original-To: current@freebsd.org 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 3585A16A47C for ; Mon, 30 Oct 2006 23:06:52 +0000 (UTC) (envelope-from jasone@FreeBSD.org) Received: from canonware.com (24-38-119-150-st.losaca.adelphia.net [24.38.119.150]) by mx1.FreeBSD.org (Postfix) with ESMTP id 44FED43DA3 for ; Mon, 30 Oct 2006 23:06:24 +0000 (GMT) (envelope-from jasone@FreeBSD.org) Received: from [192.168.168.201] (24-38-119-150-st.losaca.adelphia.net [24.38.119.150]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by canonware.com (Postfix) with ESMTP id 4A3FD1298C4; Mon, 30 Oct 2006 15:07:13 -0800 (PST) Message-ID: <45468568.8040601@FreeBSD.org> Date: Mon, 30 Oct 2006 15:06:16 -0800 From: Jason Evans User-Agent: Thunderbird 1.5.0.7 (X11/20060911) MIME-Version: 1.0 To: Poul-Henning Kamp References: <1582.1162249236@critter.freebsd.dk> In-Reply-To: <1582.1162249236@critter.freebsd.dk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Martin Cracauer , current@freebsd.org Subject: Re: Xorg leaking memory on -current... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Mon, 30 Oct 2006 23:06:52 -0000 Poul-Henning Kamp wrote: > In message <20061030225118.GA10231@cons.org>, Martin Cracauer writes: >> Poul-Henning Kamp wrote on Sun, Oct 29, 2006 at 05:01:05PM +0000: >>> After a few days my Xorg will have gobbled up most of my RAM and I have >>> to restart it to get my laptop out of VAX11/750 emulation mode. >>> >>> Has anybody else noticed this ? >> I don't run an X11 on a 7-current system. My 6-stable does certainly >> not show this, the X11 server with Firefox is up for ages. >> >> It is also unusual that you actually see that much of a slowdown, >> which means it is not a plain memory leak (in which case the leaked >> pages would never be touched again, swapped out and not impact >> performance too much). >> >> Can you post the memory map? > > Nope. /proc/$pid/map is "too large" so I don't get to see it :-( There are, AFAIK, two easy ways to get around that: 1) Use the sysutils/procmap port. 2) Use dd and specify a block size that is large enough to read the whole map in one syscall. Jason