Q: howto find xorg leak?

[D. R. Evans]

Macario Valle said the following at 04/12/2007 11:46 AM :
> Better yet;  Use top in batch mode to write top a log file every so many
> minutes, I'd try five, let it run for a while and then just go back and
> analize the data.  You will certainly find the culprit this way.  You

OK; I simply don't understand. You say that this is a certain way to find
the culprit, so I definitely want to understand it, since an assiduous
search of many advanced fora has yet to suggest a way to find the memory leak.

So if I do what you say, I will get a bunch of output in which the memory
used by xorg slowly (or not-so-slowly) increases, at the rate of a few
hundred MB per day. But how does that help solve the problem and "find the
culprit"?

I don't see how the output tells us which application is responsible for
the increasing memory usage by xorg. top would never know that; it just
looks at the process working set, and because of the way that xorg works,
even though the leak is really in the calling program, it actually evinces
itself in the xorg process.