From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Kangas Newsgroups: gmane.emacs.bugs Subject: bug#32523: 27.0.50; Emacs hangs when killing rectangle Date: Fri, 21 Aug 2020 04:51:37 -0700 Message-ID: References: <868t4vp8fv.fsf@phe.ftfl.ca> <83zhxa7tng.fsf@gnu.org> <86zhxaoerj.fsf@phe.ftfl.ca> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="6663"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: 32523@debbugs.gnu.org To: Joseph Mingrone Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Fri Aug 21 13:52:10 2020 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1k95ab-0001c8-Ok for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 21 Aug 2020 13:52:09 +0200 Original-Received: from localhost ([::1]:36400 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1k95aa-0007vn-Hr for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 21 Aug 2020 07:52:08 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:49942) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1k95aU-0007vT-5u for bug-gnu-emacs@gnu.org; Fri, 21 Aug 2020 07:52:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:33679) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1k95aT-0003v7-T4 for bug-gnu-emacs@gnu.org; Fri, 21 Aug 2020 07:52:01 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1k95aT-0008ON-S9 for bug-gnu-emacs@gnu.org; Fri, 21 Aug 2020 07:52:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Stefan Kangas Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 21 Aug 2020 11:52:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 32523 X-GNU-PR-Package: emacs Original-Received: via spool by 32523-submit@debbugs.gnu.org id=B32523.159801070532211 (code B ref 32523); Fri, 21 Aug 2020 11:52:01 +0000 Original-Received: (at 32523) by debbugs.gnu.org; 21 Aug 2020 11:51:45 +0000 Original-Received: from localhost ([127.0.0.1]:45222 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1k95aD-0008NT-8N for submit@debbugs.gnu.org; Fri, 21 Aug 2020 07:51:45 -0400 Original-Received: from mail-yb1-f193.google.com ([209.85.219.193]:33099) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1k95aB-0008NC-OA for 32523@debbugs.gnu.org; Fri, 21 Aug 2020 07:51:44 -0400 Original-Received: by mail-yb1-f193.google.com with SMTP id p191so905480ybg.0 for <32523@debbugs.gnu.org>; Fri, 21 Aug 2020 04:51:43 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:in-reply-to:references:user-agent :mime-version:date:message-id:subject:to:cc; bh=E+zlYM5137LP2skUrkDe3jclkfxGpV4RuUVPYWwwIqM=; b=FpcLITFeL1pbQA5Ao1tYuLCIyGJEpe1KHtYQ+TzhPrSAJjkHB5w8vRpDkbKn3As1Cf DcG6VJ3Nfx7/3afIOu2uXFkKwI6m2WlA9+req5wpMsk7PClCTwsmNBX0qcQsFSFkWUfs oyJoQHcr6PEwDCNzYcwM+z1ML/XGUTsHYhPFE37HjZpBIEhFfWLm9nVpZtuYzTortLuR 4Om7satOoOB95DGquF5SF4UNpRkVStMGLU+g+Du/Wo7LVEITJ2tnhIAhc/X1ktxliZpj eXAfxJBdpU5G2Q+vliAVhFfHpV0Y6FRP9HV749gPlO+PkSpZ2iEnhXsPPvvD/vkmlLRc i9rg== X-Gm-Message-State: AOAM531vj8BHBCw0y2ULGeO9fIyVsdGqdRSgYnYud7Dr0oZt6DEB8feF Q3slVkEYh2wQ8JOEuMF+T4d2LIz1SjfohqL47OHpsl0OG9YoRA== X-Google-Smtp-Source: ABdhPJxP9D3kPZTPO01hSfDGjXwQIdnBCszXD3+qeH09I301vvLzgDq2cJY7IO8lNzmEqkxLwOW/OEDNJBq7k+PYhdM= X-Received: by 2002:a25:4609:: with SMTP id t9mr3019500yba.231.1598010698347; Fri, 21 Aug 2020 04:51:38 -0700 (PDT) Original-Received: from 753933720722 named unknown by gmailapi.google.com with HTTPREST; Fri, 21 Aug 2020 04:51:37 -0700 In-Reply-To: <86zhxaoerj.fsf@phe.ftfl.ca> (Joseph Mingrone's message of "Sat, 25 Aug 2018 08:40:48 -0300") X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list 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-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:185843 Archived-At: Joseph Mingrone writes: > Eli Zaretskii writes: > >>> From: Joseph Mingrone >>> Date: Fri, 24 Aug 2018 21:59:48 -0300 > >>> Here is a recipe to make Emacs (nearly) hang indefinitely. > >>> 1. emacs -Q > >>> 2. Visit the file found https://ftfl.ca/misc/big_file_hangs_emacs.txt > >>> 3. M-x toggle-truncate-lines > >>> 4. Use rectangle-mark-mode (C-x SPC) to mark the rectangle that starts >>> at the top left of the file (point 1), and includes the leading white >>> space, the line numbers, and the space after the line numbers (point >>> 468848). > >>> 5. Kill the rectangle with C-x r k. > >>> For me, the Emacs process will continue to use 100% CPU and Emacs is >>> almost completely unresponsive and has to be killed. Some actions such >>> as saving the file may complete, but only after a few minutes. > >> It doesn't hang, it just takes very long to finish that operation (3 >> min on my machine with an unoptimized build; should be something like >> 1 to 1.5 min in an optimized build). > >> This belongs to the "Emacs is very slow with long lines" class of >> problems: the file has 2900-character lines. If this file will never >> include any text, I suggest to visit it with >> "M-x find-file-literally", then the problem of slowness will go away. > > Thanks for the `find-file-literally' tip. > > The rectangle does eventually get cut for me as well. Ignoring speed, > the problem is that Emacs is unusable afterwards. For example, if I go > away for an hour or so, then return, the Emacs process will still be > using something close to 100% CPU and trying to doing something simple, > like moving the point forward, may take minutes. Are you still seeing this behaviour? If yes, could you try to run the profiler to see what Emacs is spending so much time doing? Best regards, Stefan Kangas