GNU bug report logs - #26952
25.2; repeated buffer insertion (e.g. yank-rectangle) consumes excessive memory (4GB+ for 90MB of text)

Previous Next

Full log

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

From: Noam Postavsky <npostavs <at> users.sourceforge.net>
To: Francesco Potortì <pot <at> gnu.org>
Cc: John Wiegley <jwiegley <at> gmail.com>, Eli Zaretskii <eliz <at> gnu.org>,
 Paul Eggert <eggert <at> cs.ucla.edu>, 26952 <at> debbugs.gnu.org
Subject: Re: bug#26952: 25.1;
 loops eating all memory while yanking big rectangle
Date: Thu, 25 May 2017 13:42:39 -0400

On Thu, May 25, 2017 at 1:29 PM, Francesco Potortì <pot <at> gnu.org> wrote:
>>On Thu, May 25, 2017 at 12:48 PM, John Wiegley <jwiegley <at> gmail.com> wrote:
>>> FWIW, I too have noticed Emacs 25.2 being quite unstable. For the longest
>>> time, Emacs 24 would run for months without crashing even once. Now it crashes
>>> pretty regularly 2-4 times a day. I wonder now if I'm hitting a memory ceiling
>>> that is triggering the behavior we're describing...
>>
>>You're on macOS right? This bug and the proposed solution to be
>>backported only affects GNU/Linux distributions with recent glibc,
>>AFAIK.
>
> I'm on Debian.  I'm curious to know what did I say to make you think I'm
> on Mac :)

"You're" was referring to John Wiegley there.

>
>>Also, I don't think this bug would trigger crashes, just extreme
>>system slowness due to swapping.
>
> Well, it eats all my memory.  It is worse than a crash,

Yes, it can be. A crash only affects Emacs, the slowness affects the
whole system.

> the first time I
> had problems managing to kill Emacs.

Although as far as I could tell, a normal SIGINT is still enough to
kill Emacs, but it took around 10 or 20 seconds before it actually
took effect (due to the aforementioned system slowness).

Previous Next

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