[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Debugging memory leaks/stale references
From: |
Florian Weimer |
Subject: |
Debugging memory leaks/stale references |
Date: |
Tue, 21 Sep 2004 19:38:51 +0200 |
I've decided that it's time to track down an annoying bug in Gnus (or
Emacs). The symptom is that memory-limit keeps growing and growing,
but the data segment size (as allocated from the operating system)
remains approximately constant. In my case, this behavior is exposed
mainly when entering large NNTP groups with Gnus.
Is it possible to dump all reachable Lisp objects to a file, in the
format that is returned by princ? I could run diff(1) on two versions
of the file, and this might reveal which objects are leaking (or held
by stale references). garbage-collect output alone is not very
helpful.
(I'm going to test CVS Emacs soon, just to be sure that the behavior
is still the same. It's probably a Gnus bug, but you never know.)
- Debugging memory leaks/stale references,
Florian Weimer <=
- Re: Debugging memory leaks/stale references, Simon Josefsson, 2004/09/21
- Re: Debugging memory leaks/stale references, Richard Stallman, 2004/09/28
- Re: Debugging memory leaks/stale references, Florian Weimer, 2004/09/28
- Re: Debugging memory leaks/stale references, Florian Weimer, 2004/09/28
- Re: Debugging memory leaks/stale references, Richard Stallman, 2004/09/29