unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: jwiegley@gmail.com, 26952@debbugs.gnu.org,
	npostavs@users.sourceforge.net
Subject: bug#26952: 25.1; loops eating all memory while yanking big rectangle
Date: Fri, 26 May 2017 09:25:32 +0300	[thread overview]
Message-ID: <83wp94jfs3.fsf@gnu.org> (raw)
In-Reply-To: <a6203de2-76dd-33db-454e-417b2ed61f84@cs.ucla.edu> (message from Paul Eggert on Thu, 25 May 2017 13:59:33 -0700)

> Cc: jwiegley@gmail.com, 26952@debbugs.gnu.org, pot@gnu.org,
>  npostavs@users.sourceforge.net
> From: Paul Eggert <eggert@cs.ucla.edu>
> Date: Thu, 25 May 2017 13:59:33 -0700
> 
> On 05/25/2017 12:34 PM, Eli Zaretskii wrote:
> > What I meant is to make hybrid_malloc the default on the same systems
> > where it is the default on master, in particular on GNU/Linux systems.
> > Not sure if this is helpful enough.
> 
> I'm afraid not. This is partly why I didn't want to backport the fix: I 
> don't know what needs to be backported, and figuring that out will be 
> nontrivial.

Noam, can you please check whether building the emacs-25 branch with
HYBRID_MALLOC defined fix the problem in this bug report?  If it does,
then I think we need to arrange for HYBRID_MALLOC to be defined on ELF
based systems where DOUG_LEA_MALLOC is not defined.  I think d6585a910
on master shows the change in configure.ac which did that.  Bug#22086
holds the relevant discussions.





  reply	other threads:[~2017-05-26  6:25 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-16 14:53 bug#26952: 25.1; loops eating all memory while yanking big rectangle Francesco Potortì
2017-05-20  0:24 ` npostavs
2017-05-20  9:59   ` Eli Zaretskii
2017-05-20 17:41     ` npostavs
2017-05-20 17:59       ` Eli Zaretskii
2017-05-20 19:27         ` npostavs
2017-05-21 15:28           ` Eli Zaretskii
2017-05-21 16:00             ` npostavs
2017-05-21 16:10               ` Eli Zaretskii
2017-05-21 16:48                 ` npostavs
2017-05-21 19:15             ` Paul Eggert
2017-05-21 19:53               ` Eli Zaretskii
2017-05-21 20:20                 ` Paul Eggert
2017-05-21 20:40                   ` npostavs
2017-05-21 20:40                     ` Paul Eggert
2017-05-21 20:52                       ` npostavs
2017-05-22  4:01                   ` Eli Zaretskii
2017-05-25  5:31                     ` John Wiegley
2017-05-25 15:09                       ` Eli Zaretskii
2017-05-25 16:19                         ` Paul Eggert
2017-05-25 16:41                           ` Francesco Potortì
2017-05-25 17:20                           ` Eli Zaretskii
2017-05-27  1:15                             ` Glenn Morris
2017-05-27  6:57                               ` Paul Eggert
2017-05-27  7:42                               ` Eli Zaretskii
2017-05-25 16:48                         ` John Wiegley
2017-05-25 17:18                           ` Noam Postavsky
2017-05-25 17:29                             ` Francesco Potortì
2017-05-25 17:42                               ` Noam Postavsky
2017-05-25 17:45                           ` Eli Zaretskii
2017-05-25 19:24                             ` Paul Eggert
2017-05-25 19:34                               ` Eli Zaretskii
2017-05-25 20:59                                 ` Paul Eggert
2017-05-26  6:25                                   ` Eli Zaretskii [this message]
2017-05-26 15:24                                     ` Paul Eggert
2017-05-21 20:06               ` npostavs
2017-05-22  3:58                 ` Eli Zaretskii
2020-01-08 16:45 ` bug#26952: Possible regression of Bug#26952 - "repeated buffer insertion consumes excessive memory" Peter Ludemann
2020-01-09  0:08   ` bug#39045: Fwd: Possible regression " Peter Ludemann
2022-05-23 10:48     ` Lars Ingebrigtsen
2022-06-21 11:46       ` Lars Ingebrigtsen
2020-01-09  0:10   ` bug#26952: Possible regression of Bug#26952 " Peter Ludemann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83wp94jfs3.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=26952@debbugs.gnu.org \
    --cc=eggert@cs.ucla.edu \
    --cc=jwiegley@gmail.com \
    --cc=npostavs@users.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).