wrenkin <[EMAIL PROTECTED]> writes: > I really like Windowmaker, and the recent release of 0.80 has caused me > to give it another shot. the reason I left it was because it was a CPU > hog. Whenever I ran it, a few minutes after starting up it would shoot > to 30% CPU usage, and xfree68_s3 (The Trio64+ is not supported in Xfree > 4.1.0) would go to upwards of 60%. This is when I'm staring at a nearly > empty desktop. Nearly empty, except for an xconsole that was started > witn xdm. Maybe it's just me, but even on a p200 w/ 64MB of RAM, 100% > CPU usage at idle running an accelerated server at 24bpp doesn't sound > right. > > Today I figured out what had happened. Apparently the reason that this > was happening was that after logging in, I was turning off xconsole's > omnipresence in it's window attributes. The minute I do that CPU usage > goes from 3-5% to 100%, and it stays there. > > Does this make sense?!?
No, but it's a known bug in wmaker that's been there for a while. For me, making any window omnipresent will pin the cpu usage at 100%. I gave up on wmaker and switched to KDE. -- Brian Nelson <[EMAIL PROTECTED]> [EMAIL PROTECTED] http://bignachos.com
