Comment 12 for bug 910539

This is looking more and more like a X server resource leak.

I reached this state again after a couple of days (as I usually do) and tried to capture some information to compare with the clean-state data, so I closed everything I had open until I had only the clients that I normally have right after login. Then I started running xwininfo with different options.

After successfully running xwininfo several times I suddenly got

 Maximum number of clients reachedxwininfo: error: unable to open display ":0.0"

I literally had not run anything else other than a few shell commands. I seriously doubt xwininfo is leaking handles. Later, when I'm not doing real work, I'll try to script something to see if I can create a failure.