* H. S. Teoh <[EMAIL PROTECTED]> [070516 08:42]: > Hi, today the bug recurred. I had put in an xmessage command after > ratpoison in my .Xsession file in order to catch ratpoison crashing, so > I was able to poke around the environment a little after the crash to > determine what was going on. It appears that ratpoison is running out of > virtual memory when I hit C-t w, for some reason. I wasn't running any > memory hog except perhaps Opera, but then I never had things crashing > because of lack of memory---at least, not unless I run something that > uses a LOT of memory, and I can't imagine ratpoison opening a little > window needing *that* much memory. Just this morning I was running a > memory-hogging process that took up tens of MBs, and ratpoison didn't > have any trouble opening the window list then.
Problems with running out of memory are always hard to localize. Could you try something of the following: 1) running ratpoison in valgrind (using the --leak-check=full option) to see if that finds any memory holes (it will almost always find a bit of memory lost in the end, but that is just state information not free'd in the end but not really lost while running). (valgrind will most likely also complain about uninitialized usages in Xlibs, that is harmless, too). Running in valgrind might slow ratpoison down considerably. On a slow computer just try to run Opera or what you think it can reproduce it directly and quit then to take a look at what valgrind outputted. 2) Checking what ratpoison is actually requesting the money itself. Looking for it's pid and then looking at the Vm values in /proc/<pid>/status. This should also be possible while it runs. Intresting is if the values increase over long running of ratpoison. Hochachtungsvoll, Bernhard R. Link -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]