Date: Sat, 5 Jan 2008 12:00:28 +1100 From: Peter Jeremy <peterjeremy@optushome.com.au> To: Coleman Kane <cokane@freebsd.org> Cc: x11@freebsd.org Subject: Re: Xorg memory leak Message-ID: <20080105010028.GV947@server.vk2pj.dyndns.org> In-Reply-To: <477E48DF.9060104@FreeBSD.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>
next in thread | previous in thread | raw e-mail | index | archive | help
--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--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080105010028.GV947>