From owner-freebsd-current@FreeBSD.ORG Wed Nov 1 07:35:11 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 F423616A47B for ; Wed, 1 Nov 2006 07:35:10 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6E0E043D46 for ; Wed, 1 Nov 2006 07:35:10 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (phobos.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id kA17Z3Te060932; Wed, 1 Nov 2006 00:35:08 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <45484E26.5010408@samsco.org> Date: Wed, 01 Nov 2006 00:35:02 -0700 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.0.7) Gecko/20060910 SeaMonkey/1.0.5 MIME-Version: 1.0 To: Peter Jeremy References: <4146.1162284788@critter.freebsd.dk> <20061031172100.to3w8eww00kw84kk@webmail.leidinger.net> <4547D077.4070609@samsco.org> <20061101072543.GA849@turion.vk2pj.dyndns.org> In-Reply-To: <20061101072543.GA849@turion.vk2pj.dyndns.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on pooker.samsco.org 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Nov 2006 07:35:11 -0000 Peter Jeremy wrote: > On Tue, 2006-Oct-31 15:38:47 -0700, Scott Long wrote: >> Both Mozilla and Firefox appear to cache everything they can, without >> bounds. If you tweak a hidden pref to turn off caching, the 'leak' >> goes away. > > I don't suppose you know the name. I can't see anything obvious > in about:config > browser.cache.memory.enable on seamonkey. I recall it having a different name in the past, though. Scott