Xorg memory leak
peterjeremy at optushome.com.au
Fri Jan 4 17:00:32 PST 2008
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
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.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-x11/attachments/20080105/a37c9c33/attachment.pgp
More information about the freebsd-x11