Riccardo Mottola wrote:
The above with and without the configure option "--with-inotify" when
building GWorkspace, because, I noted that, with inotify enabled,
there was in the logs something about inotify before wmaker exited.
two different ways of checking for filesystem changes. Shouldn't be an
issue with the windowmanager (except that there could be a leak and
thus causing high memory consumption).
do you happen to use the content inspector, maybe with images? over a
lot of items?
Just guessing. I sometimes get caught in high CPU usage that doesn't go
away, but totally unrelated maybe.
Riccardo
