From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: npostavs@users.sourceforge.net Newsgroups: gmane.emacs.bugs Subject: bug#26952: 25.1; loops eating all memory while yanking big rectangle Date: Sun, 21 May 2017 12:48:28 -0400 Message-ID: <874lwegnqb.fsf@users.sourceforge.net> 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> <877f1agpz3.fsf@users.sourceforge.net> <83r2zinqbb.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1495385237 26332 195.159.176.226 (21 May 2017 16:47:17 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sun, 21 May 2017 16:47:17 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.2 (gnu/linux) Cc: eggert@cs.ucla.edu, 26952@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Sun May 21 18:47:13 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 1dCU0e-0006jC-Jh for geb-bug-gnu-emacs@m.gmane.org; Sun, 21 May 2017 18:47:12 +0200 Original-Received: from localhost ([::1]:38753 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dCU0k-0003Rs-9R for geb-bug-gnu-emacs@m.gmane.org; Sun, 21 May 2017 12:47:18 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:38854) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dCU0a-0003Ei-Jc for bug-gnu-emacs@gnu.org; Sun, 21 May 2017 12:47:13 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dCU0U-00042E-PZ for bug-gnu-emacs@gnu.org; Sun, 21 May 2017 12:47:08 -0400 Original-Received: from debbugs.gnu.org ([208.118.235.43]:56853) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dCU0U-000423-Lv for bug-gnu-emacs@gnu.org; Sun, 21 May 2017 12:47:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1dCU0U-0004bJ-0n for bug-gnu-emacs@gnu.org; Sun, 21 May 2017 12:47:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: npostavs@users.sourceforge.net Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sun, 21 May 2017 16:47:01 +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.149538521917677 (code B ref 26952); Sun, 21 May 2017 16:47:01 +0000 Original-Received: (at 26952) by debbugs.gnu.org; 21 May 2017 16:46:59 +0000 Original-Received: from localhost ([127.0.0.1]:59530 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dCU0R-0004b3-KD for submit@debbugs.gnu.org; Sun, 21 May 2017 12:46:59 -0400 Original-Received: from mail-it0-f54.google.com ([209.85.214.54]:35871) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dCU0P-0004al-Ib for 26952@debbugs.gnu.org; Sun, 21 May 2017 12:46:57 -0400 Original-Received: by mail-it0-f54.google.com with SMTP id o5so140559071ith.1 for <26952@debbugs.gnu.org>; Sun, 21 May 2017 09:46:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:from:to:cc:subject:references:date:in-reply-to:message-id :user-agent:mime-version; bh=LoR/uotZ7q/26Gxe85wpV2HHTYMgpTYgzSWltZHKkCw=; b=duZiDdasVhbRTwiextmjMJjHdynyPaWfycJmtjIAECEra53FrhbqBEex2Db7DHfk6R U1ZmUF0navCqvq1cycnopGW7j/NuSwwtsw2Hh3gOIBwZ5a4bz/5g9t3OCZV3hgYFcxdU KNR8CzUnq285uiKKxhtUebWHGF2EnPo7nyL2vJakE73BQdiROdC7YKf4NnI4f/urp3zK WY7BAO1jBV3+P0UMcuqSNaGDIaU0NGYYUYoicAtIFJeU7vLKEKKeLOpo5Ag2atxX9iwQ E+SOCoqdC41dcng+ls62qhds5NKw9Yv4RtRsZJ7OKbZMcsFuiFBX7xJJoQbUZ5FWdylL 62wQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:from:to:cc:subject:references:date :in-reply-to:message-id:user-agent:mime-version; bh=LoR/uotZ7q/26Gxe85wpV2HHTYMgpTYgzSWltZHKkCw=; b=g7ji3P25YQnMLuCIV6QGUYrSTDl/Q1l92Bqi8aWfZkPMxGvv5L1yo2wdAy7lgOYjT/ 4xvhLIu7kZxnX1BkmnxdoKWMnR2TgJ2KBqZgpwHGZH/K0z/N1dC7LOib/LlCJQgcEfFh jJsbbFQhIPE/fVimXNiC9M8/JQGAgtHMg8J1aVW27boSURmHQwguqsxRtg7B7GjCwG6c ZSg1XmXfzviPsxpyIYAXqtXHjx17ErIFr5ORI1wQ1XdzZdVvHgZ6bgtIJGDn0Nm0OewV vtksS0qOFq6P5+KQ/92il0eJj5xSJW3f0cqbh6xAXQO77tOnohYbAdWggbWahYBdl7YR 79Uw== X-Gm-Message-State: AODbwcB95Cj7PGjjK4RmoAY3xCjbtM1vAzjq8aMbPSqcv3qTw8Zkmu/R rFwvjjy4eB9SRA== X-Received: by 10.36.249.72 with SMTP id l69mr18823116ith.119.1495385211960; Sun, 21 May 2017 09:46:51 -0700 (PDT) Original-Received: from zony ([45.2.7.65]) by smtp.googlemail.com with ESMTPSA id y40sm1231204ita.2.2017.05.21.09.46.51 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Sun, 21 May 2017 09:46:51 -0700 (PDT) In-Reply-To: <83r2zinqbb.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 21 May 2017 19:10:48 +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:132704 Archived-At: Eli Zaretskii writes: > Is there src/gmalloc.o in the build directory? Yes there is. Furthermore, in 25.2 configure output shows this: Should Emacs use the GNU version of malloc? yes Should Emacs use a relocating allocator for buffers? no Should Emacs use mmap(2) for buffer allocation? no In master it says this: Should Emacs use the GNU version of malloc? no (only before dumping) Should Emacs use a relocating allocator for buffers? no Should Emacs use mmap(2) for buffer allocation? no > Does enlarge_buffer_text eventually calls into gmalloc.c in the > problematic build? Yes. > I thought we moved to system malloc in Emacs 25.2, and that was my > reading of configure, but maybe I'm confused. Everytime I try to read the configure code for this, I get more confused :(