From owner-freebsd-current@FreeBSD.ORG Mon Jan 30 21:34:39 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 E6BAE16A420 for ; Mon, 30 Jan 2006 21:34:39 +0000 (GMT) (envelope-from randy@psg.com) Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id 689F643D48 for ; Mon, 30 Jan 2006 21:34:39 +0000 (GMT) (envelope-from randy@psg.com) Received: from localhost ([127.0.0.1] helo=roam.psg.com) by rip.psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.60 (FreeBSD)) (envelope-from ) id 1F3gfW-000FiY-EN; Mon, 30 Jan 2006 21:34:38 +0000 Received: from localhost ([127.0.0.1] helo=roam.psg.com) by roam.psg.com with esmtp (Exim 4.60 (FreeBSD)) (envelope-from ) id 1F3gI6-0000gI-Ce; Mon, 30 Jan 2006 13:10:26 -0800 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17374.32961.768874.463443@roam.psg.com> Date: Mon, 30 Jan 2006 13:10:25 -0800 To: Jason Evans References: <17373.50882.270841.554876@roam.psg.com> <43DE2130.70203@yahoo.com.br> <17374.8868.815312.597508@roam.psg.com> Cc: current@freebsd.org, "Ricardo A. Reis" 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: Mon, 30 Jan 2006 21:34:40 -0000 >>> The new malloc implementation still it is going to be perfected, >>> in my station: >>> >>> Xorg increase +/- 40% >>> Firefox increase +/- 60% >>> Amule increase +/- 30% >>> >>> I not recompile this ports after world. >>> >>> Ricardo A. Reis >>> UNIFESP >>> Unix and Network Admin >> >> let me be more clear. this is a leak, not an increase. >> >> if i leave the system untouched (and it's a laptop which runs no >> net services), memory use by xorg (shown by top) slowly goes from >> under 100m to 500m in four hours. and it keeps going until it >> starts to swap. and it keeps going until it crashes the system. >> >> and this is new with build and portupgrade of 2006.01.23, a week >> ago. > > On 25 January, I checked in some malloc changes that fix some severe > fragmentation problems. Can you please try with a newer libc, and > see if the problem persists? sorry not to be sufficiently clear. i am updatin every two or three days, last was today. problem persists. randy