Hi,
Patrick Cardona wrote:
Hello,
I am puzzled with an issue with Windowmaker and GWorkspace:
For some unknown reason, a SIGTERM make wmaker process to exit and so
to kill the X session.
No, I do not experience this since a long time
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).
This happens in two very different circumstancies:
1) I noted that this happens more quickly when some removable disk is
mounted (cmd + E) on the desktop.
2) I noted also that this also happens, but for a more long delay,
without any mounted removable device. In this second case, it seems
more an idle issue, so I tried to prevent it with some xset settings,
but without success. Even I try to run InnerSpace to prevent idle
time, the SIGTERM happens... It is like the fswatcher process needs to
release some memory, and I am not able to find how to prevent it.
I tried also different way within my .xinitrc:
The latest was not more successful than the previous tries:
Are you experiencing such autoclosing of your wmaker/GWorkspace desktop ?
No. I do experience from time to time some mysterious WindowMaker
"restarts" where I see the window manager essentially dying and
restarting itself (all decorations go away and then get back). But I was
not able to correlate it with GNUstep.
From what I know, GWorkspace has no code that interacts with a
windowmanager.
Thus I see only two paths of investigation
1) GWorkspace calls something in gui/back that the window manager
dislikes and crashes (but we should pinpoint what)
2) it is not graphic related, but something just crashes and gets up to
your windowmanager. it could be some strange bug or memory consumption.
How is your session setup? Is WindowMaker strart up independent from
GWorkspace? (do you start the later after?)
It is easy to check: Exit or Log Out GWorkspace. if you are left with a
running "bare bones WindowMaker" then it is independent. If not, It
could be actually GWorkspace crashing that then terminates WindowMaker.
I would recommend the safe approach so that in case we can isolate a
GWorkspace crash or memory creep and debug that (or whatever else).
Riccardo
