unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: "Gerd Möllmann" <gerd.moellmann@gmail.com>,
	"Phil Sainty" <psainty@orcon.net.nz>
Cc: 59038@debbugs.gnu.org, Gregory Heytings <gregory@heytings.org>,
	Eli Zaretskii <eliz@gnu.org>,
	checker@d6.com
Subject: bug#59038: loading this base64 file makes emacs -Q 28.2 peg a core infinitely
Date: Sun, 6 Nov 2022 13:54:47 +0000	[thread overview]
Message-ID: <Y2e8p3D4BF7jOb5u@ACM> (raw)
In-Reply-To: <m2mt94wtf2.fsf@Mini.fritz.box>

Hello, Gerd and Phil.

On Sun, Nov 06, 2022 at 06:20:17 +0100, Gerd Möllmann wrote:
> Phil Sainty <psainty@orcon.net.nz> writes:

> > On 2022-11-06 12:41, Gregory Heytings wrote:
> >> That file opens just fine in other modes

> > It also opens fine in c-mode, with global-font-lock-mode disabled.

> >> Note that this bug has nothing to do with long lines.

> > I imagine that the font-lock issue is related to the line being
> > in excess of 21,000 chars (but general redisplay obviously doesn't
> > have problems with lines this 'small').

> > Reduced to 10,208 chars that file opens instantly under emacs -Q
> > in c-mode with font-lock enabled; but at 10,209 chars it hangs
> > Emacs (I killed it after waiting 4 minutes).

> It could also be that this is not something with the position of size,
> but with what's there at or around that position.  Just an idea.

I've identified the place in the code where it's looping, namely in the
defun c-brace-stack-at.

Gerd's Lisp backtraces earlier on in the thread were extremely helpful,
as was Phil's identification of the minimum size of buffer needed to
trigger the infinite loop.

I don't yet know why that function is looping, or why it does so only
from a certain length of buffer, but I'm working on it.

-- 
Alan Mackenzie (Nuremberg, Germany).





  reply	other threads:[~2022-11-06 13:54 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-05  2:48 bug#59038: loading this base64 file makes emacs -Q 28.2 peg a core infinitely Chris Hecker
2022-11-05  5:12 ` Gerd Möllmann
2022-11-05  7:01   ` Eli Zaretskii
2022-11-05  7:50     ` Gerd Möllmann
2022-11-05  8:21       ` Chris Hecker
2022-11-05  8:45         ` Gerd Möllmann
2022-11-05  9:30         ` Eli Zaretskii
2022-11-05 10:39           ` bug#59038: Re[2]: " Chris Hecker
2022-11-05 11:29         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-05 15:01           ` Chris Hecker
2022-11-06  5:17             ` Gerd Möllmann
2022-11-05 22:03           ` Alan Mackenzie
2022-11-06  6:00             ` Eli Zaretskii
2022-11-05  9:28       ` Eli Zaretskii
2022-11-06  5:18         ` Gerd Möllmann
2022-11-05 22:27     ` Gregory Heytings
2022-11-05 23:41       ` Gregory Heytings
2022-11-06  3:58         ` Phil Sainty
2022-11-06  5:20           ` Gerd Möllmann
2022-11-06 13:54             ` Alan Mackenzie [this message]
2022-11-06  9:18           ` Gregory Heytings
2022-11-06 13:52             ` Eli Zaretskii
2022-11-06 16:34               ` Alan Mackenzie
2022-11-07  7:55                 ` Gerd Möllmann
     [not found]               ` <Y2fiMTlfuNqae7zp@acm>
2022-11-06 19:46                 ` bug#59038: Re[2]: " Chris Hecker
2022-11-07 12:25                   ` Alan Mackenzie
2022-11-05  6:52 ` Eli Zaretskii
2022-11-05 10:45 ` Phil Sainty

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Y2e8p3D4BF7jOb5u@ACM \
    --to=acm@muc.de \
    --cc=59038@debbugs.gnu.org \
    --cc=checker@d6.com \
    --cc=eliz@gnu.org \
    --cc=gerd.moellmann@gmail.com \
    --cc=gregory@heytings.org \
    --cc=psainty@orcon.net.nz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).