From owner-freebsd-current@FreeBSD.ORG Wed Feb 1 22:48:08 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 BD5ED16A420; Wed, 1 Feb 2006 22:48:08 +0000 (GMT) (envelope-from gpalmer@freebsd.org) Received: from noop.colo.erols.net (noop.colo.erols.net [207.96.1.150]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6258B43D45; Wed, 1 Feb 2006 22:48:08 +0000 (GMT) (envelope-from gpalmer@freebsd.org) Received: from uucp by noop.colo.erols.net with local-rmail (Exim 4.52 (FreeBSD)) id 1F4Qlj-0008Yh-Rw; Wed, 01 Feb 2006 17:48:07 -0500 Received: from localhost.home.in-addr.com ([127.0.0.1]:57811) by rimmer.home.in-addr.com with esmtp (Exim 4.60 (FreeBSD)) (envelope-from ) id 1F4Qgm-0005ye-V8; Wed, 01 Feb 2006 22:43:01 +0000 Message-ID: <43E13974.8010801@freebsd.org> Date: Wed, 01 Feb 2006 22:43:00 +0000 From: Gary Palmer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20051130 X-Accept-Language: en-gb, en, en-us MIME-Version: 1.0 To: FreeBSD Current References: <17373.50882.270841.554876@roam.psg.com> <43DECB94.50307@lclark.edu> <17375.1454.11511.502872@roam.psg.com> <20060131102914.660ukp2ko4wgogoc@netchild.homeip.net> <20060201164124.GA28139@panix.com> <17377.2983.58360.592928@roam.psg.com> <20060201200221.GA31743@xor.obsecurity.org> In-Reply-To: <20060201200221.GA31743@xor.obsecurity.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit 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 22:48:08 -0000 Kris Kennaway wrote: >On Wed, Feb 01, 2006 at 11:27:35AM -0800, Randy Bush wrote: > > >>>I'm running firefox 1.5 on a fairly recent 6-STABLE, and see massive >>>memory leaks. They seem to be related to javascript. >>> >>> >>if i turn javascript off, the leak continues >> >>5000000 2053 45 1 16578 451 657355K 60K 657416K ? washingtonpo >>5000000 2053 45 1 16801 450 667667K 60K 667727K ? washingtonpo >>5000000 483 44 1 16800 143 667685K 16K 667702K ? washingtonpo >>5000000 483 44 1 16852 144 673796K 16K 673813K ? washingtonpo >>5000000 483 44 1 17023 145 677964K 16K 677981K ? washingtonpo >> >>given the inability of Jason Evans to replicate. >>we need to think a bit about a forward debugging path. >> >> > >It will presumably involve the firefox developers. > > Firefox 1.5.0.1 was recently released which contains fixes for "several memory leaks".