From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: John Wiegley Newsgroups: gmane.emacs.bugs Subject: bug#26952: 25.1; loops eating all memory while yanking big rectangle Date: Thu, 25 May 2017 09:48:47 -0700 Message-ID: References: <87zie8gyu4.fsf@users.sourceforge.net> <83h90fq269.fsf@gnu.org> <87vaovh1db.fsf@users.sourceforge.net> <8360gvpfxr.fsf@gnu.org> <87shjzgwgk.fsf@users.sourceforge.net> <83y3tqnsab.fsf@gnu.org> <83lgpqng0i.fsf@gnu.org> <83inkto7yz.fsf@gnu.org> <83lgplkm64.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1495732110 27657 195.159.176.226 (25 May 2017 17:08:30 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Thu, 25 May 2017 17:08:30 +0000 (UTC) User-Agent: Gnus/5.130016 (Ma Gnus v0.16) Emacs/25.2 (darwin) Cc: eggert@cs.ucla.edu, 26952@debbugs.gnu.org, npostavs@users.sourceforge.net To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Thu May 25 19:08:25 2017 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dDwFM-00073B-5b for geb-bug-gnu-emacs@m.gmane.org; Thu, 25 May 2017 19:08:24 +0200 Original-Received: from localhost ([::1]:32913 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dDwFR-0000z9-In for geb-bug-gnu-emacs@m.gmane.org; Thu, 25 May 2017 13:08:29 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:56988) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dDvyc-0006yx-Jc for bug-gnu-emacs@gnu.org; Thu, 25 May 2017 12:51:08 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dDvyY-0002Ev-MD for bug-gnu-emacs@gnu.org; Thu, 25 May 2017 12:51:06 -0400 Original-Received: from debbugs.gnu.org ([208.118.235.43]:35251) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dDvyY-0002En-Hh for bug-gnu-emacs@gnu.org; Thu, 25 May 2017 12:51:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1dDvyY-0006Fk-Ci for bug-gnu-emacs@gnu.org; Thu, 25 May 2017 12:51:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: John Wiegley Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 25 May 2017 16:51:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 26952 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 26952-submit@debbugs.gnu.org id=B26952.149573102423992 (code B ref 26952); Thu, 25 May 2017 16:51:02 +0000 Original-Received: (at 26952) by debbugs.gnu.org; 25 May 2017 16:50:24 +0000 Original-Received: from localhost ([127.0.0.1]:37928 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dDvxw-0006Et-7m for submit@debbugs.gnu.org; Thu, 25 May 2017 12:50:24 -0400 Original-Received: from mail-pf0-f176.google.com ([209.85.192.176]:33213) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dDvxs-0006Ef-Pz for 26952@debbugs.gnu.org; Thu, 25 May 2017 12:50:21 -0400 Original-Received: by mail-pf0-f176.google.com with SMTP id e193so172507375pfh.0 for <26952@debbugs.gnu.org>; Thu, 25 May 2017 09:50:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:in-reply-to:date:message-id:references :user-agent:mime-version; bh=Lt4Jvntm0fbHHfffKklcG1HTmwiUb/PI78wr34SH1Xs=; b=uzOSphYCCAkHKU5bjQQVefElhG3OIFEKO3ghFexlriMjFxcFbbHy1vJBRfLvp5CFWl iT+x5+6sNPgcOlEPrWEr9fNArLcZb5cWYaLCM1uA91D829VL9IhHQR3iORvccRorRgHk dIRee9r/MHc580D6A8P8bXHZQ4zMrWA4AfqY75cKy6NCKP94rbcOpAlVACODqnaJ6m/v B/ZTMS8qkWSdmd+8qdQPOBerYrQI05t0JkodoIuBJftSA3zXiwf16o9FAbWtJgzdTnvh E0qC1n1FVSfkhEuRNZmJhjChoyalYeih9EGjHpBgeluJ1wK5j28RFU2QnpejXCG0Apf8 yDJg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:in-reply-to:date:message-id :references:user-agent:mime-version; bh=Lt4Jvntm0fbHHfffKklcG1HTmwiUb/PI78wr34SH1Xs=; b=QGgaa8S5MVEAlLlpDnF5MVaWaFgcGFtbc7vWw8zDoX4gzVS5fDajHH6/NgGmC9F/HM XaFONF+eeWX6g2CscuB/NuLbOb3+W10kwyTdXp2nWHB2iUTvYfmDLY1B0JFcwpbdEfDC g5laGX06tBe18ONfRUX/hUSPXFJTJCqSmVpA83jwL9h9hZ02o+wy6ma6ayuHPZwJGdld WJIiNvI7frkudccuOs/s7sHCN0IFqXDBq3egGENs+NuGz9fVCKOXt1Abj8r2POzeE3Rk +qJQMCh8cGU+OjJaC42dD23LYuZz2Ff5QhzyKin3SLmXYI8sXHE4v/rJUulUh+c+If1i 05Yw== X-Gm-Message-State: AODbwcDSFHl4MYEUefoe/H4KwiXnuH9iSXWHS160vZ1mzYpYaci055mt 6xXtvLOPG0B9tQ== X-Received: by 10.84.140.5 with SMTP id 5mr52166327pls.113.1495731014590; Thu, 25 May 2017 09:50:14 -0700 (PDT) Original-Received: from Vulcan.local (76-234-69-149.lightspeed.frokca.sbcglobal.net. [76.234.69.149]) by smtp.gmail.com with ESMTPSA id 3sm14717882pfp.11.2017.05.25.09.50.13 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 25 May 2017 09:50:13 -0700 (PDT) X-Google-Original-From: "John Wiegley" Original-Received: by Vulcan.local (Postfix, from userid 501) id 794A44A8E51D; Thu, 25 May 2017 09:51:20 -0700 (PDT) In-Reply-To: <83lgplkm64.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 25 May 2017 18:09:55 +0300") X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:132845 Archived-At: >>>>> Eli Zaretskii writes: > We all want to accelerate the release schedule, but I don't think we know > how. That's why I don't believe we could have Emacs 26.1 out earlier than in > six months' time, basically what we had with every other .1 release. The > question is: can we afford leaving users with this nasty bug for several > months, telling them to wait. I thought we oughtn't. > But if I'm the only one who is bothered by this, so be it. I can certainly sympathize. 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... I'm OK with backporting, btw, and would be happy to test if it fixes my issues too. -- John Wiegley GPG fingerprint = 4710 CF98 AF9B 327B B80F http://newartisans.com 60E1 46C4 BD1A 7AC1 4BA2