From: Eli Zaretskii <eliz@gnu.org>
To: Colin <my.old.email.sucked@gmail.com>
Cc: 53203@debbugs.gnu.org
Subject: bug#53203: Comment with lots of color codes crashes or hangs emacs in scss-mode
Date: Wed, 12 Jan 2022 15:16:57 +0200 [thread overview]
Message-ID: <83r19d5c1i.fsf@gnu.org> (raw)
In-Reply-To: <a79a818e-b3fe-150a-a3a4-6806a7804ebd@gmail.com> (message from Colin on Wed, 12 Jan 2022 17:20:24 +1000)
> Date: Wed, 12 Jan 2022 17:20:24 +1000
> From: Colin <my.old.email.sucked@gmail.com>
>
> I have the following snippet in example.scss file:
>
> ```
>
> /*
> #ffffff #ffffff
> #ffffff #ffffff
> #ffffff #ffffff
> #ffffff #ffffff
> #ffffff #ffffff
> */
> ```
>
> On opening the file with emacs -Q (27.1 and a fresh build of git master
> (29.0.50), emacs hangs.
>
> If I remove one/two lines, it appears to burn some CPU and then work, so
> it looks like an exponential search or something.
>
> For now I'll remove the snippet from my code, but an interesting bug
> nonetheless ;)
It seems to infloop in JIT font-lock, and the culprit seems to be this
part of font-lock-keywords:
;; Even though pseudo-elements should be prefixed by ::, a
;; single colon is accepted for backward compatibility.
"\\(?:\\(:" (regexp-opt (append css-pseudo-class-ids
css-pseudo-element-ids)
t)
next prev parent reply other threads:[~2022-01-12 13:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-12 7:20 bug#53203: Comment with lots of color codes crashes or hangs emacs in scss-mode Colin
2022-01-12 13:16 ` Eli Zaretskii [this message]
2022-01-13 7:00 ` Lars Ingebrigtsen
2022-01-13 8:58 ` Eli Zaretskii
2022-05-14 10:34 ` Simen Heggestøyl
2022-05-14 12:02 ` Lars Ingebrigtsen
2022-05-14 12:38 ` Lars Ingebrigtsen
2022-05-14 13:30 ` Lars Ingebrigtsen
2022-05-14 15:33 ` Lars Ingebrigtsen
2022-05-15 10:45 ` Simen Heggestøyl
2022-05-15 12:14 ` Lars Ingebrigtsen
2022-05-15 14:46 ` Simen Heggestøyl
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=83r19d5c1i.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=53203@debbugs.gnu.org \
--cc=my.old.email.sucked@gmail.com \
/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).