From: arthur miller <arthur.miller@live.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: RE: Emacs memory usage
Date: Wed, 25 Nov 2020 00:38:55 +0000 [thread overview]
Message-ID: <AM0PR06MB6577CB2F2949742C4770579096FA0@AM0PR06MB6577.eurprd06.prod.outlook.com> (raw)
In-Reply-To: <83mtz6u42h.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1720 bytes --]
Yes, of course, I was too fast today.
How do I produce more details? Was that heaptrack something to use? I can fior a while let be to run server, and run as ordinary process if that helps. By the way does it matter if Emacs runs as sever/client or single process? Does same problem occur in both cases?
-------- Originalmeddelande --------
Från: Eli Zaretskii <eliz@gnu.org>
Datum: 2020-11-24 17:12 (GMT+01:00)
Till: Arthur Miller <arthur.miller@live.com>
Kopia: emacs-devel@gnu.org
Ämne: Re: Emacs memory usage
> From: Arthur Miller <arthur.miller@live.com>
> Cc: eliz@gnu.org
> Date: Tue, 24 Nov 2020 15:39:53 +0100
>
> I was hacking in image.c today, and was compiling Emacs several times;
> after some time I thought I saw some slowdown in term.
>
> I can see pmem is on ~74%; and Emacs is eating about 25 gig of ram.
>
> I haven't used Dired today at all.
>
> I took some pmap dump; no idea if it can help, but maybe you would like
> to look at it anyway.
Thanks, but please report this to bug#43389, where we are collecting
these data points. Also, please report the total size of the text of
all buffers and the list returned by garbage-collect, and the
information produced by malloc-info.
> 609: /home/arthur/repos/emacs/src/emacs --fg-daemon
> 000055f5616bd000 232K r---- emacs
> 000055f5616f7000 2540K r-x-- emacs
> 000055f561972000 436K r---- emacs
> 000055f5619df000 40K r---- emacs
> 000055f5619e9000 3400K rw--- emacs
> 000055f561d3b000 608K rw--- [ anon ]
> 000055f56372f000 24865608K rw--- [ anon ] <<<<<<<<<<<
The last line above is the main chunk of memory. But there's not
enough detail here to understand how is that used.
[-- Attachment #2: Type: text/html, Size: 2704 bytes --]
next prev parent reply other threads:[~2020-11-25 0:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-24 14:39 Emacs memory usage Arthur Miller
2020-11-24 14:49 ` Stefan Monnier
2020-11-24 15:08 ` Arthur Miller
2020-11-24 16:12 ` Eli Zaretskii
2020-11-24 22:06 ` Tomas Hlavaty
2020-11-25 3:31 ` Eli Zaretskii
2020-11-25 20:08 ` Tomas Hlavaty
2020-11-25 0:38 ` arthur miller [this message]
2020-11-25 3:27 ` Eli Zaretskii
2020-11-25 5:57 ` Jean Louis
2020-11-25 15:27 ` Eli Zaretskii
2020-11-25 16:01 ` Arthur Miller
2020-11-29 1:30 ` debug-warn macro [was: Re: Emacs memory usage] Adam Porter
2020-11-29 9:42 ` Stefan Kangas
2020-11-29 17:49 ` Adam Porter
2020-11-24 21:16 ` Emacs memory usage Tomas Hlavaty
2020-11-24 21:53 ` Stefan Monnier
2020-11-25 0:24 ` arthur miller
2020-11-25 0:32 ` arthur miller
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=AM0PR06MB6577CB2F2949742C4770579096FA0@AM0PR06MB6577.eurprd06.prod.outlook.com \
--to=arthur.miller@live.com \
--cc=eliz@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 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).