GNU bug report logs - #43389
28.0.50; Emacs memory leaks

Previous Next

Full log

Message #72 received at 43389 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Michael Heerdegen <michael_heerdegen <at> web.de>
Cc: 43389 <at> debbugs.gnu.org, RLAdams <at> AdamsInfoServ.Com
Subject: Re: bug#43389: 28.0.50; Emacs memory leaks
Date: Tue, 10 Nov 2020 05:30:53 +0200

> From: Michael Heerdegen <michael_heerdegen <at> web.de>
> Cc: Russell Adams <RLAdams <at> AdamsInfoServ.Com>,  43389 <at> debbugs.gnu.org
> Date: Mon, 09 Nov 2020 21:46:11 +0100
> 
> Garbage collection stats:
> ((conses 16 2645730 3784206) (symbols 48 68678 724) (strings 32 528858 451889) (string-bytes 1 18127696) (vectors 16 213184) (vector-slots 8 3704641 2189052) (floats 8 2842 5514) (intervals 56 264780 87057) (buffers 992 119))
> 
>  =>	40.4MB (+ 57.7MB dead) in conses
> 	3.14MB (+ 33.9kB dead) in symbols
> 	16.1MB (+ 13.8MB dead) in strings
> 	17.3MB in string-bytes
> 	3.25MB in vectors
> 	28.3MB (+ 16.7MB dead) in vector-slots
> 	22.2kB (+ 43.1kB dead) in floats
> 	14.1MB (+ 4.65MB dead) in intervals
> 	 115kB in buffers
> 
> Total in lisp objects:  216MB (live  123MB, dead 93.0MB)
> 
> Buffer ralloc memory usage:
> 119 buffers
> 16.1MB total (1.71MB in gaps)

Once again, the memory managed by GC doesn't explain the overall
footprint.

> Anything I can do to find out more?

If you have some tool that can produce a detailed memory map, stating
which part and which library uses what memory, please do.  Otherwise,
the most important thing is to try to describe what you did from the
beginning of the session, including the files you visited and other
features/commands you invoked that could at some point consume memory.

Thanks.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.