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? Cheers, Martin -- ----------- / http://herbert.the-little-red-haired-girl.org / ------------- =+= Was ist der Unterschied zwischen einer Bratsche und einer Waschmaschine? Die Waschmaschine vibriert, kommt erst am Ende ins Schleudern, und was rauskommt, ist sauber. -- To unsubscribe, send mail to [email protected].
