Ar an dara lá is fiche de mí Lúnasa, scríobh Mike FABIAN:
I believe that I see memory leak problems too.
Typically, XEmacs uses about 400 megabytes of virtual memory for me.
That might be a bit much but it could still be OK because I am using
many packages, Gnus, ...
But sometimes, suddenly XEmacs starts to grow until the machine grinds
to a halt be swapping madly when all 2 gigabytes of memory I have are
used up. Unfortunately I don’t know how to reproduce that, sometimes
(about once a week) it “just happens”.
What can I do to find out the reason for this when it happens next?
The naive approach is to do a M-x show-memory-usage RET and look at the
output, and see has anything evidently gone wrong. Unfortunately, that
doesn’t actually reflect XEmacs memory usage; on one 32-bit build I’m told I
have 31 MB in use, where the OS tells me it’s 85MB. If you’re particularly
lucky, the show-memory-usage figure may bear some relation to the actual OS
*Maybe* valgrind would help. I haven’t yet tried it.
On the quay of the little Black Sea port, where the rescued pair came once
more into contact with civilization, Dobrinton was bitten by a dog which was
assumed to be mad, though it may only have been indiscriminating. (Saki)
XEmacs-Beta mailing list