On Thursday 19 March 2009, Martin Dietze wrote: > Hi, > > I relatively often run across this phenomenon. When I do a full > build of the project I am working on my machine's CPU and memory > gets almost exclusively consumed by the build. During such > builds, at some point WM just restarts, i.e. the window > decorations and multiple desktops disappear and are then created > again. No harm done, the build is still running. However I'd > like to find out what's causing WM to restart. Unfortunately I > never get any useful information (like e.g. a meaningful error > message in .xsession-errorrs) from which I might start. > > Thus, just an idea: as the restarting is most likely triggered > by WM's signal handlers, could we maybe add a feature for > printing code point information or a stacktrace to stderr or a > log file before restarting?
There is no stacktrace to print. WM simply restarts because it cannot allocate memory and it exits. When it does so the wmaker watcher process senses this and restarts it. -- Dan -- To unsubscribe, send mail to [email protected].
