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

Previous Next

Package: emacs;

Reported by: Michael Heerdegen <michael_heerdegen <at> web.de>

Date: Mon, 14 Sep 2020 00:44:01 UTC

Severity: normal

Merged with 43395, 43876, 44666

Found in version 28.0.50

Done: Stefan Monnier <monnier <at> iro.umontreal.ca>

Bug is archived. No further changes may be made.

Full log


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

From: Jean Louis <bugs <at> gnu.support>
To: Michael Heerdegen <michael_heerdegen <at> web.de>
Cc: 43389 <at> debbugs.gnu.org, RLAdams <at> AdamsInfoServ.Com, schwab <at> linux-m68k.org
Subject: Re: bug#43389: 28.0.50; Emacs memory leaks
Date: Thu, 10 Dec 2020 08:43:56 +0300
* Michael Heerdegen <michael_heerdegen <at> web.de> [2020-12-10 03:51]:
> Michael Heerdegen <michael_heerdegen <at> web.de> writes:
> 
> > I think we see different symptoms.  I don't see any slow-down at all
> > (unless swapping starts, obviously).  When I do M-x garbage-collect, it
> > finishes immediately without freeing an significant amount of memory.
> 
> I must correct myself.  While this all was definitely the case the last
> time I tried to investigate this issue (one or two months ago) the
> garbage-collect statement is not true anymore.  I did M-x
> garbage-collect today when the memory was getting short and then Emacs
> froze (in the sense of "didn't respond, even to C-g"), without gkrellm
> reporting much progress, so I killed it (after 20 seconds or so - aeons
> for a computer).
> 
> I did not experience a slowdown, however (maybe I've faster RAM?).

One time I waited for 36 minutes and it completed the garbage collection.





This bug report was last modified 4 years and 57 days ago.

Previous Next


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