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 Datum: 2020-11-24 17:12 (GMT+01:00) Till: Arthur Miller Kopia: emacs-devel@gnu.org Ämne: Re: Emacs memory usage > From: Arthur Miller > 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.