From: Wes Hardaker <wes@hardakers.net>
Subject: something memory related definitely going on lately.
Date: Thu, 05 Jun 2003 10:42:24 -0700 [thread overview]
Message-ID: <sdk7c0h14v.fsf@wanderer.hardakers.net> (raw)
hardaker 1867 2.3 44.4 212296 113472 ? S 06:29 5:49 xemacs -f gnus
^^^^^^^^^^^^^
A 113Mb emacs is, um, not good (even for XEmacs).
My normal tricks, however, for finding memory leaks:
(progn
(insert "\n")
(mapcar (function (lambda (z)
(insert (format "%s:\n" (buffer-name z)))
(mapcar (function
(lambda (x) (insert (format " %s %s\n"
(symbol-name (car x))
(cdr x)))))
(buffer-memory-usage z)) z))
(buffer-list t)))
Doesn't turn up anything really really huge buffer wise... Is there a
function to get a lits of all current variables in use? That could
then help determine the size of maybe an "overweight" variable.
--
"In the bathtub of history the truth is harder to hold than the soap,
and much more difficult to find." -- Terry Pratchett
next reply other threads:[~2003-06-05 17:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-05 17:42 Wes Hardaker [this message]
2003-06-06 4:32 ` John Paul Wallington
2003-06-06 6:55 ` Kai Großjohann
2003-10-18 1:35 ` Lars Magne Ingebrigtsen
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=sdk7c0h14v.fsf@wanderer.hardakers.net \
--to=wes@hardakers.net \
/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 NNTP newsgroup(s).