This is another 'I don't know if it helps but...' message. I was led to this page because I have a simple screensaver script that just uses xloadimage to paint into the root window and it has the same resource leakage problem. This leakage is reproducable if you just put xscreensaver.programs: xloadimage -quiet -onroot -center file.jpg in your .Xresources. Set the cycle time to something short and run xscreensaver-command -activate, wait for it to cycle (in this case just reloads the same image). Then check with xrestop and there's a new <unknown>. Repeat; same result, each cycle adds another <unknown>. If you don't wait for the cycle timeout, no <unknown> is created.
As far as I know this sort of thing is *supposed* to work with xscreensaver. i.e. any application that can just draw to a virtual root can be used as a screensaver (xv is even mentioned as an example on the man page). I don't know enough about xscreensaver to go hunting further, but someone who does might decide that it is reasonable at this point to report this as an xscreensaver bug. I don't know if it's isolated to debian. I've reproduced this on 2 different sarge installations. I don't have anything running unstable right now. Cheers, -Dean Townsley -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
