Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

3
  • xrestop is certainly a nice tool, but does not seem to indicate the cpu usage, caused by that application (there does not seem to be a memory leak, only a computation leak .. so to speak). Could you elaborate how I can figure out the client application that causes trouble with xrestop? Commented Aug 1, 2011 at 2:41
  • 1
    If you can find some unexpected growth of the amount of resources used by a client over time, then you have a suspect (xrestop shows the pid of the process and/or X identifier). If nothing shows up, probably the issue is internal to the X server. Commented Aug 1, 2011 at 10:26
  • For what it's worth, I followed this answer and used xrestop to figure out why Xorg is killing me, and it turned out xcompmgr was the reason. Killing it made the problem go away completely, in htop, Xorg has very low CPU usage now. Commented Jan 31, 2019 at 16:14