From: Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: How to debug elisp memory leak
Date: Fri, 17 Sep 2004 18:14:28 GMT [thread overview]
Message-ID: <jwvk6uszs0p.fsf-monnier+gnu.emacs.help@gnu.org> (raw)
In-Reply-To: 2hzn3qz30q.fsf@vserver.cs.uit.no
> 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.
I don't think there's a quick answer to this.
But for a start, can you try the pckage below?
It provides a command M-x memory-usage which will show what Emacs's heap is
made of (whic proportion is cons cells, buffer text, strings, arrays, ...).
It's not much info, but it's a start: when you get the "lisp pointer size
exceeded" thingy, hit M-x memory-usage and post the result here.
Also, try then to kill (lots of or even all) buffers and re-run M-x
memory-usage and post that result as well.
Stefan
PS: Better to hit M-x memory-usage at least once before to make sure it
works and is already loaded and ready to be used.
;;; memory-usage.el --- Analyze the memory usage of Emacs in various ways
;; Copyright (C) 2002, 2004 Free Software Foundation, Inc.
;; Author: Stefan Monnier <monnier@cs.yale.edu>
;; Keywords: maint
;; This file is free software; you can redistribute it and/or modify
;; it under the terms of the GNU General Public License as published by
;; the Free Software Foundation; either version 2, or (at your option)
;; any later version.
;; This file is distributed in the hope that it will be useful,
;; but WITHOUT ANY WARRANTY; without even the implied warranty of
;; MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
;; GNU General Public License for more details.
;; You should have received a copy of the GNU General Public License
;; along with GNU Emacs; see the file COPYING. If not, write to
;; the Free Software Foundation, Inc., 59 Temple Place - Suite 330,
;; Boston, MA 02111-1307, USA.
;;; Commentary:
;;
;;; Code:
(defun buffer-size-bytes (b)
"Return total number of bytes in the buffer contents."
(with-current-buffer b
(save-restriction
(widen)
(- (position-bytes (point-max)) (position-bytes (point-min))))))
(defun buffer-gap-bytes (b)
"Return total number of bytes in the buffer gap."
(with-current-buffer b
(gap-size)))
(defun buffer-total-bytes (b)
"Return total number of ralloc bytes used by buffer."
(with-current-buffer b
(save-restriction
(widen)
(+ (position-bytes (point-max))
(- (position-bytes (point-min)))
(gap-size)))))
;;;###autoload
(defun memory-usage ()
"List all buffers and their memory usage."
(interactive)
(pop-to-buffer (get-buffer-create "*Buffer Details*"))
(erase-buffer)
(let* ((bufs (buffer-list))
(num (length bufs))
(gc-stats (garbage-collect))
(conses (nth 0 gc-stats))
(symbols (nth 1 gc-stats))
(markers (nth 2 gc-stats))
(strings (nth 3 gc-stats))
(vectors (nth 4 gc-stats))
(floats (nth 5 gc-stats))
(intervals (nth 6 gc-stats)))
(insert (format "Garbage collection stats:\n%s\n\n =>" gc-stats))
(insert (format "\t%d bytes in cons cells\n" (* 8 (+ (car conses) (cdr conses)))))
(insert (format "\t%d bytes in symbols\n" (* 24 (+ (car symbols) (cdr symbols)))))
(insert (format "\t%d bytes in markers\n" (* 20 (+ (car markers) (cdr markers)))))
(insert (format "\t%d bytes of string chars\n" strings))
(insert (format "\t%d bytes of vector slots\n" (* 4 vectors)))
(insert (format "\t%d bytes in floats\n" (* 12 (+ (car floats) (cdr floats)))))
(insert (format "\t%d bytes in intervals\n" (* 28 (+ (car intervals) (cdr intervals)))))
(insert (format "\nTotal bytes in lisp objects (not counting string and vector headers): %d\n\n"
(+ (* 8 (+ (car conses) (cdr conses)))
(* 24 (+ (car symbols) (cdr symbols)))
(* 20 (+ (car markers) (cdr markers)))
strings
vectors
(* 12 (+ (car floats) (cdr floats)))
(* 28 (+ (car intervals) (cdr intervals))))))
(insert (format "Buffer ralloc memory usage:\n%d buffers\n%d bytes total (%d in gaps)\n"
num
(apply #'+ (mapcar #'buffer-total-bytes bufs))
(apply #'+ (mapcar #'buffer-gap-bytes bufs))))
(insert (format "%10s\t%s\t%s\n\n" "Size" "Gap" "Name"))
(insert (mapconcat
(lambda (b)
(format "%10d\t%s\t%s"
(buffer-size-bytes b)
(buffer-gap-bytes b)
(buffer-name b)))
(sort bufs (lambda (b1 b2)
(> (buffer-size-bytes b1) (buffer-size-bytes b2))))
"\n"))
(insert "\n"))
(goto-char (point-min)))
(provide 'memory-usage)
;; arch-tag: 04e012f0-3c59-4319-8d1a-e86204671ec5
;;; memory-usage.el ends here
next prev parent reply other threads:[~2004-09-17 18:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-16 14:45 How to debug elisp memory leak Frode Vatvedt Fjeld
2004-09-17 18:14 ` Stefan Monnier [this message]
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=jwvk6uszs0p.fsf-monnier+gnu.emacs.help@gnu.org \
--to=monnier@iro.umontreal.ca \
/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).