From owner-freebsd-x11@FreeBSD.ORG Wed Jan 21 06:11:44 2004 Return-Path: Delivered-To: freebsd-x11@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9D11116A4CE; Wed, 21 Jan 2004 06:11:44 -0800 (PST) Received: from hex.athame.co.uk (guru164.netsonic.fi [194.29.193.164]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1E6B243D41; Wed, 21 Jan 2004 06:11:41 -0800 (PST) (envelope-from andy@athame.co.uk) Received: from vimes.int.athame.co.uk ([192.168.1.3]) by hex.athame.co.uk with esmtp (Exim 4.30; FreeBSD) id 1AjJ4y-000IUA-NW; Wed, 21 Jan 2004 16:11:36 +0200 From: Andy Fawcett To: Jonathan Fosburgh , Eric Anholt Date: Wed, 21 Jan 2004 16:11:51 +0200 User-Agent: KMail/1.5.4 References: <200401160820.19794.jonathan@fosburgh.org> <1074277065.725.4.camel@leguin> <200401210801.31483.jonathan@fosburgh.org> In-Reply-To: <200401210801.31483.jonathan@fosburgh.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200401211611.51849.andy@athame.co.uk> cc: freebsd-x11@freebsd.org cc: kde@FreeBSD.org Subject: Re: Possible memory leak in XFree86 X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Jan 2004 14:11:44 -0000 On Wednesday 21 January 2004 16:01, Jonathan Fosburgh wrote: > Adding kde@ and following up below. > > Now, contrast this to my setup at home where I use konqueror and keep > it running all the time. As I state above, there are relatively few > differences aside from -CURRENT at work and -STABLE at home and > hardware, which it seems should not be an issue. Now who knows, > maybe this will magically stop when 3.2-RELEASE comes out, but given > this has been happening for awhile (and across several releases), I'm > not too confident of that happening. I also find it odd that I would > be the only one seeing this. Is there anything further I can do to > try to figure out what is going on? Are you using Qt3.3b1 by any chance? It is known that this causes massive memory leaks under some situations? A. -- Andy Fawcett | andy@athame.co.uk | tap@kde.org "In an open world without walls and fences, | tap@lspace.org we wouldn't need Windows and Gates." -- anon | tap@fruitsalad.org