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 01:21:34 -0700 Message-ID: References: <83h6zd51h0.fsf@gnu.org> <9719cff6-4534-46d9-0fed-1476633ac37d@gmail.com> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="0000000000007e995705ecb4e19f" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="28759"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 59038@debbugs.gnu.org, acm@muc.de, Eli Zaretskii To: Gerd =?UTF-8?Q?M=C3=B6llmann?= Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sat Nov 05 09:22:29 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 1orERg-0007HS-UN for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 05 Nov 2022 09:22:29 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1orERJ-0000kG-4L; Sat, 05 Nov 2022 04:22:05 -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 1orERH-0000i4-Ba for bug-gnu-emacs@gnu.org; Sat, 05 Nov 2022 04:22:03 -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 1orERH-0000UI-2u for bug-gnu-emacs@gnu.org; Sat, 05 Nov 2022 04:22:03 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1orERG-0000ZV-MO for bug-gnu-emacs@gnu.org; Sat, 05 Nov 2022 04:22:02 -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 08:22:02 +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.16676365142178 (code B ref 59038); Sat, 05 Nov 2022 08:22:02 +0000 Original-Received: (at 59038) by debbugs.gnu.org; 5 Nov 2022 08:21:54 +0000 Original-Received: from localhost ([127.0.0.1]:55406 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1orER7-0000Z4-UE for submit@debbugs.gnu.org; Sat, 05 Nov 2022 04:21:54 -0400 Original-Received: from mail-yw1-f171.google.com ([209.85.128.171]:40563) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1orER4-0000Yp-PQ for 59038@debbugs.gnu.org; Sat, 05 Nov 2022 04:21:52 -0400 Original-Received: by mail-yw1-f171.google.com with SMTP id 00721157ae682-36a4b86a0abso62672197b3.7 for <59038@debbugs.gnu.org>; Sat, 05 Nov 2022 01:21: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=CFLO3rIqQM5atXTtTumvA49w2Ff6KXIaDnW2fpc91Mg=; b=lrNbxtBoSqRg9K81kSU4n8RFJSUuOQl7P3+9cotSaa+OZvcmBJUcM3+xAfVOKO6OzY /wUwqKCQ+s2Q1yDx4x/wpfnLTsTTN3OuzwS/3jd2CRR2AejFQg0jrORZtoRELpzIZn5i 88qMySrENbPaQ4xdtEBBr9rBEfHE02QIbWA+3cSl3/0GZ9VLxiUetDnJvU8H1Xaw949A ei1Dnz/zt8Bq3RAgydT51HPAXFjLUS48MgjPD0Y6kthmLKgqpLeUbmYHvd09Xv9HqIM4 ZvOmeCHlvrB8JdETM9DN5CRyeucA00TWjhZEhNjqxqOPsh7NjNevCDstMRuk44/UW3SF XuZA== 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=CFLO3rIqQM5atXTtTumvA49w2Ff6KXIaDnW2fpc91Mg=; b=XqAw+SwyWXdNVWsw0hU2b8kevyE03RNYu0e+WbRkpF6lPryvWLM3gNh99IBScQ/RqO sG5UvLtaZQLRyN3kkEr8B2+nNfqD9Sc7mgMk81PZrxira0bYs8SzXU9pcCLXYcVr8Ob+ wT1gAKyKB0hrfOyu1ehG7x3fnRzf97x3ROkC1Kz3zFYeXRj6HIqFQhwf+Wtpy48mzoZx 8JCNAPO/lffF6oE1vWcxHAKx4A1LPDya+5ZEfv/No7xXxrAkFpgeY0jfr7uzy9R1zf8/ iGXqQG7IgKqESpccmalg3NvmVAP4p/6HEvhT+sYkDwHu9uKlPhCEmV2F79jQJnAAxGN3 a7lw== X-Gm-Message-State: ACrzQf1Qq57KeWxCuOrhkIPvZB244+xz6Sr1Dmr8CSkWeUYG/uAtS+9o BXvWyr1QjtsmVgHF2VJpvWytSXwCjLsji7XIWkkHEA== X-Google-Smtp-Source: AMsMyM56ZLrT87kMy9OPo1LCfWujqD3A5QShG9ruF9cXRdvcwY1hG3SsT0OslWCOMjd351pqFDR/Ec+0/ZpEseIpWFs= X-Received: by 2002:a81:704a:0:b0:370:3daf:4e89 with SMTP id l71-20020a81704a000000b003703daf4e89mr35814597ywc.268.1667636504985; Sat, 05 Nov 2022 01:21:44 -0700 (PDT) In-Reply-To: <9719cff6-4534-46d9-0fed-1476633ac37d@gmail.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:247137 Archived-At: --0000000000007e995705ecb4e19f Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable > It's a single 21,728-character line. Yeah? This isn=E2=80=99t 1970. I have 32gb of ram and a 12 core cpu. It= =E2=80=99s a bug. It should either parse the file (instantly, it=E2=80=99s 27kb) 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. 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 even think ctrl-g worked for me. Chris On Sat, Nov 5, 2022 at 00:50 Gerd M=C3=B6llmann = wrote: > On 05.11.22 08:01, Eli Zaretskii wrote: > > What is reproducible, exactly? > > I don't understand. The infinite loop is reproducible, "pegging one > core" as he expressed it, using up one CPU core. > > > Visiting the file is almost > > instantaneous here, in Emacs 29. What did you do to get Emacs into an > > infloop? > > Maybe I switched applications with Cmd-TAB, or something else triggering > redisplay. Do a M-x or C-l. > > > It is IMO unreasonable to expect CC Mode to do something sensible with > > random sequence of characters that don't resemble C in any way. > > I think no-one expects that. The bug is the uninterruptable loop or > whatever causes it. > --0000000000007e995705ecb4e19f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

>=C2=A0It's a single 21,728-character line.
<= div dir=3D"auto">
<= /span>
Yeah?=C2=A0 This isn=E2=80=99t 1970.=C2=A0 I have 32gb of ram and a= 12 core cpu. =C2=A0 It=E2=80=99s a bug.=C2=A0 It should either parse the f= ile (instantly, it=E2=80=99s 27kb) or it should at least stop after a few m= s and tell me it=E2=80=99s lame and needs me to switch manually to another = mode.=C2=A0 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.