all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Florian Weimer <fw@deneb.enyo.de>
Subject: Debugging memory leaks/stale references
Date: Tue, 21 Sep 2004 19:38:51 +0200	[thread overview]
Message-ID: <87d60fjzdg.fsf@deneb.enyo.de> (raw)

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.)

             reply	other threads:[~2004-09-21 17:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-21 17:38 Florian Weimer [this message]
2004-09-21 19:49 ` Debugging memory leaks/stale references Simon Josefsson
2004-09-27 19:40   ` Florian Weimer
2004-09-27 19:52     ` Stefan Monnier
2004-09-27 20:36       ` Florian Weimer
2004-09-27 20:49         ` Stefan Monnier
2004-09-27 20:48       ` Simon Josefsson
2004-09-28 15:20     ` Richard Stallman
2004-09-28 21:00       ` Florian Weimer
2004-09-28 21:51         ` Florian Weimer
2004-09-29 16:39         ` Richard Stallman
2004-09-29 23:51         ` Kenichi Handa
2004-09-28 21:40       ` Kim F. Storm
2004-09-21 19:57 ` Stefan Monnier
2004-09-21 21:01   ` Florian Weimer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87d60fjzdg.fsf@deneb.enyo.de \
    --to=fw@deneb.enyo.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.