From owner-freebsd-current@FreeBSD.ORG  Tue Oct 31 08:53:12 2006
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 38F5A16A407
	for <current@freebsd.org>; Tue, 31 Oct 2006 08:53:12 +0000 (UTC)
	(envelope-from phk@critter.freebsd.dk)
Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222])
	by mx1.FreeBSD.org (Postfix) with ESMTP id CC55343D70
	for <current@freebsd.org>; Tue, 31 Oct 2006 08:53:11 +0000 (GMT)
	(envelope-from phk@critter.freebsd.dk)
Received: from critter.freebsd.dk (critter.freebsd.dk [192.168.48.2])
	by phk.freebsd.dk (Postfix) with ESMTP id 2E435170C5;
	Tue, 31 Oct 2006 08:53:10 +0000 (UTC)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by critter.freebsd.dk (8.13.8/8.13.8) with ESMTP id k9V8r8do004147;
	Tue, 31 Oct 2006 08:53:09 GMT (envelope-from phk@critter.freebsd.dk)
To: Peter Jeremy <peterjeremy@optushome.com.au>
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
In-Reply-To: Your message of "Tue, 31 Oct 2006 19:50:07 +1100."
	<20061031085007.GA1466@turion.vk2pj.dyndns.org> 
Date: Tue, 31 Oct 2006 08:53:08 +0000
Message-ID: <4146.1162284788@critter.freebsd.dk>
Sender: phk@critter.freebsd.dk
Cc: 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
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Oct 2006 08:53:12 -0000

In message <20061031085007.GA1466@turion.vk2pj.dyndns.org>, Peter Jeremy writes
:
>
>--17pEHd4RhPHOinZp
>Content-Type: text/plain; charset=us-ascii
>Content-Disposition: inline
>Content-Transfer-Encoding: quoted-printable
>
>On Sun, 2006-Oct-29 17:01:05 +0000, Poul-Henning Kamp wrote:
>>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 ?
>
>My -current is quite out of date and I don't run normally run X on it
>but my $0.02:
>
>Are you using jemalloc or phkmalloc?  Does fiddling with MALLOC_OPTIONS
>have any effect?  Have you hit an edge case somewhere?

jemalloc, MALLOC_OPTIONS=aj

>Do you have any long-running clients?  X clients can store objects in
>the server and some web browsers have been known to simulate Xserver
>leaks.

It certainly correlates with firefox, but restarting firefox does
not relieve the memory pressure.

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.