From owner-freebsd-gnome@FreeBSD.ORG Mon Mar 26 16:41:19 2007 Return-Path: X-Original-To: gnome@freebsd.org Delivered-To: freebsd-gnome@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1CD4A16A401 for ; Mon, 26 Mar 2007 16:41:19 +0000 (UTC) (envelope-from marcus@freebsd.org) Received: from av-tac-rtp.cisco.com (hen.cisco.com [64.102.19.198]) by mx1.freebsd.org (Postfix) with ESMTP id BEA2D13C45E for ; Mon, 26 Mar 2007 16:41:18 +0000 (UTC) (envelope-from marcus@freebsd.org) X-TACSUNS: Virus Scanned Received: from rooster.cisco.com (localhost [127.0.0.1]) by av-tac-rtp.cisco.com (8.11.7p3+Sun/8.11.7) with ESMTP id l2QGfHb08262; Mon, 26 Mar 2007 12:41:17 -0400 (EDT) Received: from [192.168.1.9] (jclarke-vpn.cisco.com [172.18.173.17]) by rooster.cisco.com (8.11.7p3+Sun/8.11.7) with ESMTP id l2QGfEq13050; Mon, 26 Mar 2007 12:41:17 -0400 (EDT) Message-ID: <4607F7A9.6070100@freebsd.org> Date: Mon, 26 Mar 2007 12:41:13 -0400 From: Joe Marcus Clarke Organization: FreeBSD, Inc. User-Agent: Thunderbird 1.5.0.10 (Macintosh/20070221) MIME-Version: 1.0 To: Mike Harding References: <20070326162037.C830D17065@bsd.mvh> In-Reply-To: <20070326162037.C830D17065@bsd.mvh> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: gnome@freebsd.org Subject: Re: gconfd-2 memory usage is HUGE (100M!) X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GNOME for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Mar 2007 16:41:19 -0000 Mike Harding wrote: > I still have problems with gconfd chewing up insane amounts of memory. > It's currently 100 M, 92 M resident. Is there any way to diagnose > what's going on? Is this possibly being driven by my use of > Evolution, which is hanging in there about 112M (50M resident)? You could try setting malloc ktrace trace points, and running ktrace on it to see where the memory is going. I'm not seeing anything strange here, so it may be due to some bad gconf XML files. Joe -- Joe Marcus Clarke FreeBSD GNOME Team :: gnome@FreeBSD.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome