From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Chris Hecker Newsgroups: gmane.emacs.bugs Subject: bug#59038: loading this base64 file makes emacs -Q 28.2 peg a core infinitely Date: Sat, 5 Nov 2022 08:01:33 -0700 Message-ID: References: <83h6zd51h0.fsf@gnu.org> <9719cff6-4534-46d9-0fed-1476633ac37d@gmail.com> <87tu3dabbw.fsf@yahoo.com> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="000000000000f7d8a305ecba77f8" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="20561"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 59038@debbugs.gnu.org, Gerd =?UTF-8?Q?M=C3=B6llmann?= , Eli Zaretskii , acm@muc.de To: Po Lu Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sat Nov 05 16:02:13 2022 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 1orKgX-00059s-G7 for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 05 Nov 2022 16:02:13 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1orKgO-0005Y5-1x; Sat, 05 Nov 2022 11:02:04 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1orKgM-0005XY-KN for bug-gnu-emacs@gnu.org; Sat, 05 Nov 2022 11:02:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1orKgM-0005wQ-CK for bug-gnu-emacs@gnu.org; Sat, 05 Nov 2022 11:02:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1orKgL-0001CY-RV for bug-gnu-emacs@gnu.org; Sat, 05 Nov 2022 11:02:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Chris Hecker Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 05 Nov 2022 15:02:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 59038 X-GNU-PR-Package: emacs Original-Received: via spool by 59038-submit@debbugs.gnu.org id=B59038.16676605134601 (code B ref 59038); Sat, 05 Nov 2022 15:02:01 +0000 Original-Received: (at 59038) by debbugs.gnu.org; 5 Nov 2022 15:01:53 +0000 Original-Received: from localhost ([127.0.0.1]:57813 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1orKgD-0001C9-DK for submit@debbugs.gnu.org; Sat, 05 Nov 2022 11:01:53 -0400 Original-Received: from mail-yw1-f169.google.com ([209.85.128.169]:36481) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1orKgA-0001Bu-3g for 59038@debbugs.gnu.org; Sat, 05 Nov 2022 11:01:51 -0400 Original-Received: by mail-yw1-f169.google.com with SMTP id 00721157ae682-37063f855e5so68000987b3.3 for <59038@debbugs.gnu.org>; Sat, 05 Nov 2022 08:01:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=d6-com.20210112.gappssmtp.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=ju+kTmYs76ITCppMF717dk6tTyHQHZQ1jHeAqnEpVxU=; b=7Pbb/cfnI/iZMXJGhI2XCwyLSEf1aN/0YDiDQoLpZBVFYyj3BRQbxYfcLOD051o0sS mJm6bQ7liz6Nt/cenC48I88Pn5ppmji/Hj+QAMEqhSNI5kZZRNblpm4Kf+bAxVhP7VvT HD8+5I8f0Uv94GaEaFbiXeEgsrFmIE+vin5bFIybmNvGdNzbmigFGwZN0O+BAS+6z7R7 0dOik0naK8pjSKegrhvUYLByQewf14u4aWq+0DA8+Y3EN92GW7fsZXI4ycgxzffeVl7X gEKlELrz1ZXfugAgS2KVHMdxkAZgCcnv1WpkOIhtjWMAB7adSVkoK8Fn8xB9pLImrltF roEg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=ju+kTmYs76ITCppMF717dk6tTyHQHZQ1jHeAqnEpVxU=; b=j787j74CKfplRnjhH9dmmIkyuH+DsE9LmAdAoq9FmXIT03wWyFSUYqRlYVbMxJTyeN ETDGtUxSd29iTn56I/ozibVl8rypWu8twNqsppL6gXBEfPXc8e6vQku0ZayhFWvsNcas oRBsGT1X2fwzDPKxDMy5C/2BOjFAXnyMbWXG2T3zwz4wcSD5cnjIGz5XD6Ri8ZP2OilA g7fDFez1rm3Gme/naI0/YSN0fsh53jyK0hJnCylL2fdjRbnCwNfcJKbUz5AvfeOYkVbK PyEH02vBJT5d7WzpdzH2mOVN91Qtdp2JLM1rJmRCj9JUN8Jr8GG1Yu6+vCjkpq9lEWm4 /ErA== X-Gm-Message-State: ACrzQf3kH7kfdAR/+W+/BE1pdowaCP/zBUuzWhehFPCoaS/tq9OrdzxR 8U0s0B5EXIK3Xujm+4zUiesMT8i85Rxe2q5vjGAdDg== X-Google-Smtp-Source: AMsMyM79giTCLM1kK++38sic6TtGPPD8LECVY1goA7rFnFDZW8IKTICpdNJPR8pLjfCYGRKhOMoTuD/sTwjrVB1GRBU= X-Received: by 2002:a81:de43:0:b0:368:ee18:f9c3 with SMTP id o3-20020a81de43000000b00368ee18f9c3mr38036480ywl.322.1667660504350; Sat, 05 Nov 2022 08:01:44 -0700 (PDT) In-Reply-To: <87tu3dabbw.fsf@yahoo.com> 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: , Original-Sender: "bug-gnu-emacs" Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:247148 Archived-At: --000000000000f7d8a305ecba77f8 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable >> (instantly, it=E2=80=99s 27kb) > Which is a lot, even in this day and age. I don't even know what to say to this. Literally every other editor I tried including the immense pile that is visual studio opened this file instantly, including ones that do syntax highlighting. I love emacs but holy cow you need to renormalize what you think a modern computer is capable of so your performance expectations for emacs are more realistic. Anyway, I=E2=80=99m glad it=E2=80=99s fixed in 29. Chris On Sat, Nov 5, 2022 at 04:29 Po Lu wrote: > Chris Hecker writes: > > > Yeah? This isn=E2=80=99t 1970. > > Emacs becoming unusable due to long lines has been fixed in Emacs 29. > > > I have 32gb of ram and a 12 core cpu. > > Physical memory and the number of processors installed does not really > matter here, unfortunately, as Emacs only uses one processor to process > your (27kb) file. > > > (instantly, it=E2=80=99s 27kb) > > Which is a lot, even in this day and age. > > > or it should at least stop after a few ms and tell me it=E2=80=99s lame= and > > needs me to switch manually to another mode. > > A few ms is shorter than a roundtrip to and fro the X server over my > current connection. But: > > > I mean, given the 28.2 user experience, there is no opportunity to > > switch to fundamental mode because emacs was hosed. I don=E2=80=99t ev= en > > think ctrl-g worked for me. > > All of this is no longer a problem in Emacs 29, and even if you somehow > still cause redisplay to become wedged, you can set max-redisplay-ticks > to a suitable value. > --000000000000f7d8a305ecba77f8 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

>> (instantly= , it=E2=80=99s 27kb)
> Which is a lot, even in this day and age.
<= /div>

= I don't even know what to say to this.=C2=A0 Literally every other edit= or I tried including the immense pile that is visual studio opened this fil= e instantly, including ones that do syntax highlighting.

I love emacs but holy cow you need to reno= rmalize what you think a modern computer is capable of so your performance = expectations for emacs are more realistic.

Anyway, I=E2=80=99m glad it=E2=80=99s fixed in 29. =C2= =A0

Chris

On Sat, Nov 5, 2022 at 04:29 Po Lu <luangruo@yahoo.com> wrote:
Chris Hecker <checker@d6.com> writes:

> Yeah?=C2=A0 This isn=E2=80=99t 1970.

Emacs becoming unusable due to long lines has been fixed in Emacs 29.

> I have 32gb of ram and a 12 core cpu.

Physical memory and the number of processors installed does not really
matter here, unfortunately, as Emacs only uses one processor to process
your (27kb) file.

> (instantly, it=E2=80=99s 27kb)

Which is a lot, even in this day and age.

> or it should at least stop after a few ms and tell me it=E2=80=99s lam= e and
> needs me to switch manually to another mode.

A few ms is shorter than a roundtrip to and fro the X server over my
current connection.=C2=A0 But:

> I mean, given the 28.2 user experience, there is no opportunity to
> switch to fundamental mode because emacs was hosed.=C2=A0 I don=E2=80= =99t even
> think ctrl-g worked for me.

All of this is no longer a problem in Emacs 29, and even if you somehow
still cause redisplay to become wedged, you can set max-redisplay-ticks
to a suitable value.
--000000000000f7d8a305ecba77f8--