From: Frode Vatvedt Fjeld <frodef@cs.uit.no>
Subject: How to debug elisp memory leak
Date: Thu, 16 Sep 2004 16:45:09 +0200 [thread overview]
Message-ID: <2hzn3qz30q.fsf@vserver.cs.uit.no> (raw)
I'm regularly getting the "lisp pointer size exceeded" warning after
about one week of running emacs. When this happens, nothing I do, such
as killing buffers, seems to help much; at most I can postpone the
inevitable crash for a few more minutes of work.
I figure there's a memory leak; somewhere there's e.g a global
variable with an ever-growing list of whatever. But I have no idea
where to start looking for what or where this might be. Can anyone
help me?
I'm using GNU Emacs 21.3.1, but this behavior has been consistent for
at least a few months and minor versions of emacs.
Thanks,
--
Frode Vatvedt Fjeld
next reply other threads:[~2004-09-16 14:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-16 14:45 Frode Vatvedt Fjeld [this message]
2004-09-17 18:14 ` How to debug elisp memory leak Stefan Monnier
2004-09-20 12:23 ` Frode Vatvedt Fjeld
2004-10-02 10:33 ` Frode Vatvedt Fjeld
2004-10-02 10:51 ` Frode Vatvedt Fjeld
2004-10-02 11:15 ` Frode Vatvedt Fjeld
2004-10-04 14:33 ` Stefan Monnier
2004-10-03 12:53 ` 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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2hzn3qz30q.fsf@vserver.cs.uit.no \
--to=frodef@cs.uit.no \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).