From: Paul Eggert <eggert@cs.ucla.edu>
To: Eli Zaretskii <eliz@gnu.org>
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 08:24:48 -0700 [thread overview]
Message-ID: <7412f6c0-0467-fae5-819c-b78173cd3c4d@cs.ucla.edu> (raw)
In-Reply-To: <83wp94jfs3.fsf@gnu.org>
On 05/25/2017 11:25 PM, Eli Zaretskii wrote:
> I think d6585a910
> on master shows the change in configure.ac which did that. Bug#22086
> holds the relevant discussions.
I was worried that that was the change you wanted (and was hoping it
would be a different one :-).
We can't merely install that change. We also need at least some of the
commits that fixed significant problems associated with that change,
such as 09ece4d, 3d82a8e, a4817d8, a39a03a, dd951c0, 2ee2963, 7fdc3cf,
a4817d8, e4cd4a7, e1a9f20, 874c59a, 384ffef, dec1390, a39a03a, cb22fce.
Not all of them are strictly necessary, but it'd be better to install
the whole batch than start a new development project in this area.
The above list of changes was reasonably easy to generate. The hard part
will be identifying any followup changes that are also necessary but are
not immediately obvious. So it's quite possible that if we take this
approach we will need to publish Emacs 25.3, wait for allocation-related
bug reports to roll in, and then publish Emacs 25.4 and so forth.
next prev parent reply other threads:[~2017-05-26 15:24 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
2017-05-26 15:24 ` Paul Eggert [this message]
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=7412f6c0-0467-fae5-819c-b78173cd3c4d@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=26952@debbugs.gnu.org \
--cc=eliz@gnu.org \
--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).