reopen 423141 thanks 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.
The message I'm getting is: ratpoison: Virtual memory exhausted [2] Abort ratpoison Strangely enough, after restarting ratpoison several times (while keeping the xmessage open so the session won't logout), the problem went away. All I did during that time was to save an email I was in the middle of typing (only ~200 lines, in mutt, which is text-based, so again I can't imagine how that could make a difference). Memory usage while the crash was happening: MemTotal: 255164 kB MemFree: 28648 kB Buffers: 15784 kB Cached: 100048 kB SwapCached: 21264 kB Active: 152716 kB Inactive: 62508 kB SwapTotal: 120476 kB SwapFree: 51108 kB Dirty: 0 kB Writeback: 0 kB AnonPages: 91168 kB Mapped: 22316 kB Slab: 7724 kB SReclaimable: 3048 kB SUnreclaim: 4676 kB PageTables: 1136 kB NFS_Unstable: 0 kB Bounce: 0 kB CommitLimit: 248056 kB Committed_AS: 682740 kB VmallocTotal: 777940 kB VmallocUsed: 9328 kB VmallocChunk: 768524 kB Memory usage after things started working again: MemTotal: 255164 kB MemFree: 29304 kB Buffers: 17892 kB Cached: 101952 kB SwapCached: 21524 kB Active: 150060 kB Inactive: 64584 kB SwapTotal: 120476 kB SwapFree: 52460 kB Dirty: 24 kB Writeback: 0 kB AnonPages: 86412 kB Mapped: 19588 kB Slab: 7744 kB SReclaimable: 3048 kB SUnreclaim: 4696 kB PageTables: 1124 kB NFS_Unstable: 0 kB Bounce: 0 kB CommitLimit: 248056 kB Committed_AS: 674644 kB VmallocTotal: 777940 kB VmallocUsed: 9328 kB VmallocChunk: 768524 kB I don't see that much of a difference in memory usage, so I'm not convinced that it's simply because I have too little RAM. I suspect there may be some other factor that perhaps triggers a bug in ratpoison causing it to try to allocate an unusually large amount of memory. --T -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
