From owner-freebsd-current@FreeBSD.ORG Wed Feb 1 18:22:12 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 38AD416A422 for ; Wed, 1 Feb 2006 18:22:12 +0000 (GMT) (envelope-from jasone@freebsd.org) Received: from lh.synack.net (lh.synack.net [204.152.188.37]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4764D43D7B for ; Wed, 1 Feb 2006 18:22:01 +0000 (GMT) (envelope-from jasone@freebsd.org) Received: by lh.synack.net (Postfix, from userid 100) id 2460C5E48EE; Wed, 1 Feb 2006 10:22:01 -0800 (PST) Received: from [192.168.168.203] (moscow-cuda-gen2-68-64-60-20.losaca.adelphia.net [68.64.60.20]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by lh.synack.net (Postfix) with ESMTP id 214A65E48BB; Wed, 1 Feb 2006 10:21:56 -0800 (PST) In-Reply-To: <17374.36245.570152.464206@roam.psg.com> References: <17373.50882.270841.554876@roam.psg.com> <43DE2130.70203@yahoo.com.br> <17374.8868.815312.597508@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> Mime-Version: 1.0 (Apple Message framework v746.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <00D8C07F-FA95-47B6-9EF9-6C25652E93D2@freebsd.org> Content-Transfer-Encoding: 7bit From: Jason Evans Date: Wed, 1 Feb 2006 10:21:53 -0800 To: Randy Bush X-Mailer: Apple Mail (2.746.2) X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on lh.synack.net X-Spam-Level: * X-Spam-Status: No, score=1.8 required=5.0 tests=RCVD_IN_NJABL_DUL, RCVD_IN_SORBS_DUL autolearn=no version=3.0.4 Cc: current@freebsd.org, Kris Kennaway 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 18:22:12 -0000 On Jan 30, 2006, at 2:05 PM, Randy Bush wrote: >>> and the Xorg one just keeps growing and growing and growing. >> That's a different matter though. > > and that's my point > >> PID USERNAME THR PRI NICE SIZE RES STATE TIME WCPU >> COMMAND >> 2166 randy 4 20 0 166M 108M kserel 3:51 0.00% >> firefox-bin >> 1343 randy 1 96 0 126M 83500K select 2:44 2.00% >> Xorg >> 1394 randy 4 20 0 102M 51456K kserel 0:08 0.00% >> nautilus > > and now > > PID USERNAME THR PRI NICE SIZE RES STATE TIME WCPU > COMMAND > 2166 randy 4 20 0 166M 110M kserel 4:26 0.00% > firefox-bin > 1343 randy 1 96 0 142M 86032K select 3:14 2.39% Xorg > 1394 randy 4 20 0 102M 51456K kserel 0:08 0.00% > nautilus > > notice the growth in xorg and only xorg. > > and, from x's pov, all i have been doing is typing in an emacs window, > thought there are 42 other windows open. > > and it will just keep growing if i walk away for a few hours. 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. Neither number has increased this morning (other than fluctuations when launching/terminating firefox). I see no evidence that jemalloc is doing anything wrong, or that Xorg's memory usage is excessive when utilizing jemalloc. Perhaps gnome is causing issues for you. In any case, I'm not going to look into this any further unless someone provides concrete, detailed evidence that jemalloc is behaving badly. Thanks, Jason