From owner-freebsd-x11@FreeBSD.ORG Sat Jan 5 01:00:31 2008 Return-Path: Delivered-To: x11@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DFD3316A49A; Sat, 5 Jan 2008 01:00:31 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail01.syd.optusnet.com.au (mail01.syd.optusnet.com.au [211.29.132.182]) by mx1.freebsd.org (Postfix) with ESMTP id 6B8AD13C457; Sat, 5 Jan 2008 01:00:31 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from server.vk2pj.dyndns.org (c220-239-20-82.belrs4.nsw.optusnet.com.au [220.239.20.82]) by mail01.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id m0510SWf025026 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 5 Jan 2008 12:00:29 +1100 Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by server.vk2pj.dyndns.org (8.14.2/8.14.1) with ESMTP id m0510SUl021476; Sat, 5 Jan 2008 12:00:28 +1100 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.14.2/8.14.2/Submit) id m0510SAi021475; Sat, 5 Jan 2008 12:00:28 +1100 (EST) (envelope-from peter) Date: Sat, 5 Jan 2008 12:00:28 +1100 From: Peter Jeremy To: Coleman Kane Message-ID: <20080105010028.GV947@server.vk2pj.dyndns.org> References: <477BBB39.6070208@FreeBSD.org> <20080102182923.GM903@server.vk2pj.dyndns.org> <477C1750.9050506@FreeBSD.org> <20080103184014.GP947@server.vk2pj.dyndns.org> <20080104075037.GA25510@demeter.hydra> <477E48DF.9060104@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="NqSa+Xr3J/G6Hhls" Content-Disposition: inline In-Reply-To: <477E48DF.9060104@FreeBSD.org> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.17 (2007-11-01) Cc: x11@freebsd.org Subject: Re: Xorg memory leak X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jan 2008 01:00:32 -0000 --NqSa+Xr3J/G6Hhls Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jan 04, 2008 at 09:55:27AM -0500, Coleman Kane wrote: >I assume that whatever is allocating space inside of Xorg is also >supposed to have a corresponding free() call, and perhaps this is not >being done. I would expect Xorg, however, to be able to track this >information according to client socket handles, and automatically free() >when the client that requested these allocations disconnects. In >addition, xrestop is (from my understanding) *supposed to* be able to >track these allocation requests, but it doesn't seem to be doing that. This suggests that either the X server is allocating memory but not associating it with resources reported to xrestop or is failing to correctly free resources when the associated clients exit. Ideally, you want to find something that lets you reproducably cause a leak without requiring massive X traffic. If it only shows up under very high load, it may be indicative of a race condition. If you want to debug this further, you might also be interested in ports/x11/xmon which will allow you to monitor the client<->server protocol. --=20 Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. --NqSa+Xr3J/G6Hhls Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFHftas/opHv/APuIcRAm8YAJ0Y0Ewj++vwTSkPmmtEu3soOCpq4gCfRkdn wCYj7jQY/qt2GQa82vH/xDk= =Y/f9 -----END PGP SIGNATURE----- --NqSa+Xr3J/G6Hhls--