unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: jwiegley@gmail.com, Paul Eggert <eggert@cs.ucla.edu>,
	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 21:15:32 -0400	[thread overview]
Message-ID: <ff60gn14nf.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <E1dAdrD-000863-Bw@tucano.isti.cnr.it>

Eli Zaretskii wrote:

>> Cc: 26952@debbugs.gnu.org, pot@gnu.org, npostavs@users.sourceforge.net
>> From: Paul Eggert <eggert@cs.ucla.edu>
>> Date: Thu, 25 May 2017 09:19:50 -0700
>> 
>> We can publish 26.1 earlier if we don't run it through our leisurely six 
>> month test period.
>
> There's no leisure in our pretests.  We need to wait until the bug
> reports come in after each pretest tarball, that's all.  It takes time
> for the reports to come in because Emacs is a very large package that
> supports many different use patterns.

Idle speculation:

If a ~ six month testing process doesn't show up the fairly fundamental
memory issues that cropped up in both 25.1 and 25.2 soon after release,
then perhaps it isn't time well spent. Perhaps people would be better
served by more frequent, smaller releases. I have the feeling (not
backed up by any data) that pretest use is declining, with people just
using master or releases. Perhaps switching things around so that
releases come from master (and development happens on a branch) would
help, but maybe not.





  reply	other threads:[~2017-05-27  1:15 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 [this message]
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
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=ff60gn14nf.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=26952@debbugs.gnu.org \
    --cc=eggert@cs.ucla.edu \
    --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).