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

Previous Next

Full log

Message #41 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: pipcet <at> protonmail.com, 75672 <at> debbugs.gnu.org
Subject: Re: bug#75672: 31.0.50; scratch/igc memory usage/collection issues
Date: Mon, 20 Jan 2025 14:59:40 +0200

> Cc: 75672 <at> debbugs.gnu.org
> Date: Mon, 20 Jan 2025 02:34:11 +0000
> From:  Alexis Purslane via "Bug reports for GNU Emacs,
>  the Swiss army knife of text editors" <bug-gnu-emacs <at> gnu.org>
> 
> I rebuilt Emacs with lucid instead of GTK just for the hell of it, and
> it's still exhibiting exorbitant monotonicly increasing memory usage, so
> I don't think it's GTK. I've had one Emacs open for about two hours,
> just with GNUS open in it, doing nothing, on another workspace, and it's
> using 533MB. The one I'm using for messing around with SLY and Common
> Lisp is using 1.5GB currently, and I've seen it reach similar hights
> without an inferior lisp running so I don't think it's that. Still
> waiting for a freeze to happen again to attach GDB to it. 

Is this memory really used, or is that just the free memory glibc
keeps to itself and doesn't return to the system?  Can you show the
output of "M-x malloc-info" from the session with 1.5GB footprint?
Does "M-x malloc-trim" make the memory footprint smaller?

Previous Next

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