From: emacs user <user.emacs@gmail.com>
To: "Jan Djärv" <jan.h.d@swipnet.se>
Cc: emacs-devel@gnu.org
Subject: Re: Memory again
Date: Thu, 22 Dec 2011 20:54:08 +0200 [thread overview]
Message-ID: <CAK16+CfXYoi3Kiq9WBQLtpWZbf8WxFkn69oVS2sse2UWuUFwDA@mail.gmail.com> (raw)
In-Reply-To: <CAK16+CfMr2pjkjpvVX2wJMtQst3chNWQAWH5YFvRjWrY-vrhhA@mail.gmail.com>
On Thu, Dec 22, 2011 at 4:58 PM, emacs user <user.emacs@gmail.com> wrote:
> On Thu, Dec 22, 2011 at 4:08 PM, Jan Djärv <jan.h.d@swipnet.se> wrote:
>>
>> 21 dec 2011 kl. 18:55 skrev emacs user:
>>
>>>
>>> Thanks... The leaks command indeed reports zero leaks now. however,
>>> emacs still grows every time I invoke vm. here is a memory report
>>> which I get after killing all buffers, when emacs is 214 Mb large (as
>>> seen in the Activity Monitor). is this normal?
>>>
>>
>> As I'm not a vm-user I can't really say. But it sounds like something is not released back to the OS.
>>
>> Jan D.
>
> how does one go about diagnosing this? is it possible to tell if this
> an elisp problem or a c-problem?
Just in case this is helpful in diagnosing this:
- The problem (rapidly growing memory and eventual crash) occurs also
with emacs -nw on mac os x.
- I tested, and as far as I can tell, this does not occur under GNU/Linux
>>> Garbage collection stats:
>>> ((400287 . 303593) (45615 . 144) (60632 . 80546) 2488080 600138 (708 .
>>> 477) (521 . 271) (85624 . 67826))
>>>
>>> => 6404592+4857488 bytes in cons cells
>>> 2189520+6912 bytes in symbols
>>> 2425280+3221840 bytes in markers
>>> 11328+7632 bytes in floats
>>> 29176+15176 bytes in intervals
>>> 2739968+2170432 bytes in string headers
>>> 2488080 bytes of string chars
>>> 2488080 bytes of vector slots
>>>
>>> Total bytes in lisp objects: 27167562 (live 16888082, dead 10279480)
>>>
>>> Buffer ralloc memory usage:
>>> 14 buffers
>>> 29463 bytes total (24346 in gaps)
>>> Size Gap Name
>>>
>>> 2186 987 *srecode-map-tmp*
>>> 2186 1814 *code-converting-work*
>>> 565 1570 *Buffer Details*
>>> 170 1851 *Deletions*
>>> 30 2000 *Messages*
>>> 25 2019 *extract address components*
>>> 22 2022 *canonical address*
>>> 16 5812 *code-conversion-work*
>>> 11 2040 *Echo Area 1*
>>> 0 2022 *Minibuf-1*
>>> 0 20 *vm-nonexistent-summary*
>>> 0 20 *Minibuf-0*
>>> 0 2055 *Echo Area 0*
>>> 0 20 *subst-char-in-string*
>>
next prev parent reply other threads:[~2011-12-22 18:54 UTC|newest]
Thread overview: 87+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-20 6:34 Memory again emacs user
2011-12-20 7:43 ` Eli Zaretskii
2011-12-20 12:05 ` emacs user
2011-12-20 13:04 ` Eli Zaretskii
2011-12-20 22:07 ` Jan Djärv
2011-12-21 8:07 ` Jan Djärv
2011-12-21 10:39 ` Carsten Mattner
2011-12-21 17:55 ` emacs user
2011-12-22 14:08 ` Jan Djärv
2011-12-22 14:58 ` emacs user
2011-12-22 18:54 ` emacs user [this message]
2011-12-22 19:15 ` Jan Djärv
2011-12-23 4:41 ` YAMAMOTO Mitsuharu
2012-01-17 10:04 ` emacs user
2012-01-17 10:58 ` YAMAMOTO Mitsuharu
2012-01-17 13:14 ` emacs user
2012-01-18 1:30 ` YAMAMOTO Mitsuharu
2011-12-22 23:09 ` Carsten Mattner
2011-12-23 0:39 ` Stefan Monnier
2011-12-23 10:44 ` emacs user
2012-01-05 6:13 ` emacs user
2012-01-05 22:37 ` Jan Djärv
2012-01-06 9:58 ` emacs user
2012-01-06 11:10 ` Carsten Mattner
-- strict thread matches above, loose matches on Subject: below --
2011-12-19 19:51 emacs user
2011-12-20 5:32 ` Dmitry Antipov
2012-01-06 14:28 ` Chong Yidong
2012-01-06 15:53 ` emacs user
2011-11-26 13:26 Carsten Mattner
2011-11-26 13:28 ` Carsten Mattner
2011-11-26 14:35 ` Dmitry Antipov
2011-11-26 14:48 ` Eli Zaretskii
2011-11-26 17:37 ` Dmitry Antipov
2011-11-26 20:19 ` Eli Zaretskii
2011-11-26 14:58 ` Carsten Mattner
2011-11-26 16:23 ` Eli Zaretskii
2011-11-26 19:02 ` Carsten Mattner
2011-11-26 20:31 ` Eli Zaretskii
2011-11-26 21:00 ` Eli Zaretskii
2011-11-27 10:29 ` Carsten Mattner
2011-11-27 10:43 ` Andreas Schwab
2011-11-27 13:53 ` Carsten Mattner
2011-11-27 13:11 ` Eli Zaretskii
2011-11-27 13:53 ` Carsten Mattner
2011-11-27 16:44 ` Eli Zaretskii
2011-11-27 17:37 ` Carsten Mattner
2011-11-27 17:59 ` Carsten Mattner
2011-12-06 4:02 ` Óscar Fuentes
2011-12-06 5:08 ` Eli Zaretskii
2011-12-06 9:35 ` Carsten Mattner
2011-12-06 10:24 ` Dmitry Antipov
2011-12-06 13:07 ` Eli Zaretskii
2011-12-06 13:29 ` Stefan Monnier
2011-12-06 17:20 ` Eli Zaretskii
2011-12-06 20:25 ` Stefan Monnier
2011-12-07 7:52 ` Eli Zaretskii
2011-12-07 8:15 ` Dmitry Antipov
2011-12-07 13:06 ` Eli Zaretskii
2011-12-07 14:01 ` Stefan Monnier
2011-12-08 17:30 ` Carsten Mattner
2011-12-09 3:39 ` Dmitry Antipov
2011-12-09 13:52 ` Carsten Mattner
2011-12-06 13:12 ` Eli Zaretskii
2011-12-06 16:28 ` Óscar Fuentes
2011-12-06 19:53 ` Stefan Monnier
2011-12-11 17:49 ` Nix
2011-12-15 3:52 ` Tim Connors
2011-12-15 4:09 ` Eli Zaretskii
2011-12-15 4:38 ` Tim Connors
2011-12-15 5:52 ` Eli Zaretskii
2011-12-15 4:50 ` Óscar Fuentes
2011-12-15 6:04 ` Eli Zaretskii
2011-12-16 21:55 ` Stefan Monnier
2011-12-17 17:40 ` Nix
2011-12-18 15:13 ` Dmitry Antipov
2011-12-19 1:34 ` Stefan Monnier
2011-12-19 8:28 ` Dmitry Antipov
2011-12-19 11:26 ` Stefan Monnier
2012-01-23 16:49 ` Nix
2012-01-25 16:19 ` Ted Zlatanov
2011-11-26 17:54 ` Dmitry Antipov
2011-11-26 18:47 ` martin rudalics
2011-11-26 19:09 ` Carsten Mattner
2011-11-28 4:27 ` Stefan Monnier
2011-11-28 9:24 ` Carsten Mattner
2011-11-28 15:31 ` Davis Herring
2011-11-28 21:33 ` Carsten Mattner
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=CAK16+CfXYoi3Kiq9WBQLtpWZbf8WxFkn69oVS2sse2UWuUFwDA@mail.gmail.com \
--to=user.emacs@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=jan.h.d@swipnet.se \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).