From: David Kastrup <dak@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: mem leak
Date: Mon, 24 Apr 2006 05:37:36 +0200 [thread overview]
Message-ID: <854q0jk5j3.fsf@lola.goethe.zz> (raw)
In-Reply-To: <buoy7xv4pl2.fsf@dhapc248.dev.necel.com> (Miles Bader's message of "Mon, 24 Apr 2006 12:31:05 +0900")
Miles Bader <miles.bader@necel.com> writes:
> Does anybody have advice for finding a memory leak in emacs?
>
> Recent builds seems to have some leak: even with only a few small
> buffers open, Emacs rapidly consumes more and more memory (to the point
> where the system eventually becomes unusable).
garbage-collect is an interactive built-in function in `C source code'.
(garbage-collect)
Reclaim storage for Lisp objects no longer needed.
Garbage collection happens automatically if you cons more than
`gc-cons-threshold' bytes of Lisp data since previous garbage collection.
`garbage-collect' normally returns a list with info on amount of space in use:
((USED-CONSES . FREE-CONSES) (USED-SYMS . FREE-SYMS)
(USED-MARKERS . FREE-MARKERS) USED-STRING-CHARS USED-VECTOR-SLOTS
(USED-FLOATS . FREE-FLOATS) (USED-INTERVALS . FREE-INTERVALS)
(USED-STRINGS . FREE-STRINGS))
However, if there was overflow in pure space, `garbage-collect'
returns nil, because real GC can't be done.
[back]
This might help tracking down what kind of memory is consumed, and
whether it is Lisp-visible.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2006-04-24 3:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-24 3:31 mem leak Miles Bader
2006-04-24 3:37 ` David Kastrup [this message]
2006-04-24 4:15 ` Miles Bader
-- strict thread matches above, loose matches on Subject: below --
2006-04-24 7:33 LENNART BORGMAN
2006-04-24 8:01 ` Miles Bader
2006-04-24 8:18 ` Romain Francoise
2006-04-24 8:26 ` Miles Bader
2006-04-24 8:39 ` Miles Bader
2006-04-24 12:24 ` Stefan Monnier
2006-04-24 14:44 ` Miles Bader
2006-04-24 17:52 ` Richard Stallman
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=854q0jk5j3.fsf@lola.goethe.zz \
--to=dak@gnu.org \
--cc=emacs-devel@gnu.org \
/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.