From owner-freebsd-current@FreeBSD.ORG Wed Feb 1 23:34:46 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 848DD16A420 for ; Wed, 1 Feb 2006 23:34:46 +0000 (GMT) (envelope-from josh.carroll@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.195]) by mx1.FreeBSD.org (Postfix) with ESMTP id 96C5943D83 for ; Wed, 1 Feb 2006 23:34:04 +0000 (GMT) (envelope-from josh.carroll@gmail.com) Received: by xproxy.gmail.com with SMTP id s9so184104wxc for ; Wed, 01 Feb 2006 15:34:04 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=GrMF/KFiBiJmVui5Cd9pKUzAgfwbomK5G6qMFBdCD1HFQi479w+QObF04hpJqaDruetOX5O3NTLaKe1HhbmoZg5Z+Zxrp0E9s+NviPkaHcxGXqdgjRqA1dj1qZLJsnArPKuhZk7En3ypsqbitxaeQT/GbsZoATwsu95PD4p9lyk= Received: by 10.70.92.1 with SMTP id p1mr111976wxb; Wed, 01 Feb 2006 15:34:03 -0800 (PST) Received: by 10.70.27.17 with HTTP; Wed, 1 Feb 2006 15:34:03 -0800 (PST) Message-ID: <8cb6106e0602011534n85f3373p8f31cdf34dfacb2@mail.gmail.com> Date: Wed, 1 Feb 2006 15:34:03 -0800 From: Josh Carroll Sender: josh.carroll@gmail.com To: current@freebsd.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <17373.50882.270841.554876@roam.psg.com> <17374.32961.768874.463443@roam.psg.com> <20060130214226.GA68308@xor.obsecurity.org> <17374.35319.265698.476631@roam.psg.com> <20060130215408.GA68492@xor.obsecurity.org> <17374.36245.570152.464206@roam.psg.com> <00D8C07F-FA95-47B6-9EF9-6C25652E93D2@freebsd.org> <17377.14732.391882.775974@roam.psg.com> Cc: Subject: Re: xorg 6.9.0 mem leak 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 Feb 2006 23:34:46 -0000 Assuming it is the pixmaps being cached by firefox causing this growth, can someone with this problem please see this thread: http://forums.mozillazine.org/viewtopic.php?t=3D354828#memcache And set the maximum memory cache to 8000 or 16000, then see if this problem persists? The quick way to do this is: about:config Create a new integer key, named "browser.cache.memory.capacity" and assign a value in KB for the cache size. You can confirm the size set by opening: about:cache You should see: Maximum storage size: 16000 KiB (or whatever you set it to). Watching xrestop, the Pxm mem value for Firefox should not exceed your maximum set. If it remains below your value, but you still see X.org or Firefox consuming/leaking memory, it may be an entirely different problem, but I suspect this will fix the problem. Josh On 2/1/06, Matt Reimer wrote: > On 2/1/06, Randy Bush wrote: > > > I've been running Xorg, firefox, and emacs, since last night (with > > > jemalloc's redzone code enabled) on a two-day-old -current build, and > > > after many invocations of firefox and emacs, with serious attempts to > > > make firefox use lots of memory, Xorg's, memory usage has stabilized > > > at ~75 MB mapped, and ~35 MB resident. > > > > what seems to be common with those of us seeing leakage is multiple > > windows and many tabs. i standardly have three windows each with > > six to ten tabs. > > Maybe what's eating up the memory is Firefox 1.5's new feature to > cache extra data in RAM in order to make Back/Forward fast. > > Matt > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org= " >