GNU bug report logs - #75672
31.0.50; scratch/igc memory usage/collection issues

Previous Next

Package: emacs;

Reported by: Alexis Purslane <alexispurslane <at> pm.me>

Date: Sun, 19 Jan 2025 17:01:02 UTC

Severity: normal

Found in version 31.0.50

Done: Pip Cet <pipcet <at> protonmail.com>

Bug is archived. No further changes may be made.

Full log


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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Alexis Purslane <alexispurslane <at> pm.me>
Cc: 75672 <at> debbugs.gnu.org
Subject: Re: bug#75672: 31.0.50; scratch/igc memory usage/collection issues
Date: Mon, 20 Jan 2025 21:35:15 +0200
> Date: Mon, 20 Jan 2025 19:05:45 +0000
> From: Alexis Purslane <alexispurslane <at> pm.me>
> Cc: 75672 <at> debbugs.gnu.org
> 
> "Eli Zaretskii" <eliz <at> gnu.org> writes:
> 
> > Does "M-x malloc-trim" make the memory footprint smaller?
> 
> I haven't had an Emacs session open long enough in a bit to get it up to
> 1.3GB again, but I did have a 550MB session open, so I ran M-x
> malloc-trim on it. That brought it back down to 407MB of resident memory.

Then this is almost certainly the usual modus operandi of glibc, and
malloc-trim was added to Emacs precisely for these cases.  For
absolute certainty, use "M-x malloc-info" and examine the resulting
report to determine which part of the malloc arena is in the free
lists.

I see no problems here, and nothing that MPS does which we didn't see
in Emacs before.




This bug report was last modified 81 days ago.

Previous Next


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