From owner-freebsd-current@FreeBSD.ORG Wed Feb 1 16:41:25 2006 Return-Path: X-Original-To: freebsd-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 E60C416A422 for ; Wed, 1 Feb 2006 16:41:25 +0000 (GMT) (envelope-from dscheidt@panix.com) Received: from mail1.panix.com (mail1.panix.com [166.84.1.72]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8535943D4C for ; Wed, 1 Feb 2006 16:41:25 +0000 (GMT) (envelope-from dscheidt@panix.com) Received: from panix1.panix.com (panix1.panix.com [166.84.1.1]) by mail1.panix.com (Postfix) with ESMTP id 93D2658B3A; Wed, 1 Feb 2006 11:41:24 -0500 (EST) Received: (from dscheidt@localhost) by panix1.panix.com (8.11.6p3/8.8.8/PanixN1.1) id k11GfOO15956; Wed, 1 Feb 2006 11:41:24 -0500 (EST) Date: Wed, 1 Feb 2006 11:41:24 -0500 From: David Scheidt To: Alexander Leidinger Message-ID: <20060201164124.GA28139@panix.com> References: <17373.50882.270841.554876@roam.psg.com> <43DECB94.50307@lclark.edu> <17375.1454.11511.502872@roam.psg.com> <20060131102914.660ukp2ko4wgogoc@netchild.homeip.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060131102914.660ukp2ko4wgogoc@netchild.homeip.net> User-Agent: Mutt/1.5.10i Cc: Randy Bush , Eric Anholt , FreeBSD Current 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 16:41:26 -0000 On Tue, Jan 31, 2006 at 10:29:14AM +0100, Alexander Leidinger wrote: > Date: Tue, 31 Jan 2006 10:29:14 +0100 > From: Alexander Leidinger > To: Randy Bush > Cc: Eric Anholt , > FreeBSD Current > Subject: Re: xorg 6.9.0 mem leak > > Randy Bush wrote: > > >>Note that any app leaking pixmaps or other X resources will > >>have those resources charged to X, not the app. xrestop can > >>find offenders usually if it's some app's fault. > > > >so it's firefox. thanks. > > I can confirm that I see something like this too. At work on Solaris 10 with > Firefox 1.5 I notice a sudden death of firefox when I let BigBrother refresh I'm running firefox 1.5 on a fairly recent 6-STABLE, and see massive memory leaks. They seem to be related to javascript.