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 #33 received at 26952 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: npostavs <at> users.sourceforge.net
Cc: pot <at> gnu.org, 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: Sun, 21 May 2017 19:10:48 +0300

> From: npostavs <at> users.sourceforge.net
> Cc: Paul Eggert <eggert <at> cs.ucla.edu>,  26952 <at> debbugs.gnu.org,  pot <at> gnu.org
> Date: Sun, 21 May 2017 12:00:00 -0400
> 
> Eli Zaretskii <eliz <at> gnu.org> writes:
> 
> > I cannot see why.  AFAIK, the only difference between using the hybrid
> > allocation and not using it is before Emacs is dumped; after that both
> > use the same system malloc.
> 
> I was under the impression that it's just the opposite: master is using
> hybrid malloc which means to use system malloc *after* dumping, and
> emacs-25 is using the custom non-system malloc *after* dumping.

By "custom non-system malloc" do you mean gmalloc.c?  Is there
src/gmalloc.o in the build directory?  (I don't have access to a
system when this happens, my GNU/Linux build doesn't have
src/gmalloc.o.)  Does enlarge_buffer_text eventually calls into
gmalloc.c in the problematic build?

I thought we moved to system malloc in Emacs 25.2, and that was my
reading of configure, but maybe I'm confused.

Previous Next

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