From: Eli Zaretskii <eliz@gnu.org>
To: Nick Urbanik <nicku@nicku.org>
Cc: 62794@debbugs.gnu.org
Subject: bug#62794: 28.2; jit-lock-function enters busy loop when open """ near top of large Python program
Date: Thu, 13 Apr 2023 07:58:25 +0300 [thread overview]
Message-ID: <83jzyg5qfi.fsf@gnu.org> (raw)
In-Reply-To: <ZDdE/j6dDbhCw1QF@nicku.org> (message from Nick Urbanik on Thu, 13 Apr 2023 09:55:42 +1000)
> Date: Thu, 13 Apr 2023 09:55:42 +1000
> From: Nick Urbanik <nicku@nicku.org>
> Cc: 62794@debbugs.gnu.org
>
> >Please post such a file, or a URL where it could be downloaded. I
> >couldn't easily find such a large file on my system.
>
> It turns out that it is not the size, but some pathological
> arrangement of the code. I have provided a much smaller sample here
> that I can reproduce the problem with by:
>
> 1. Move the cursor to below the from elesewhere import ... line.
> 2. Press Enter
> 3. Type:
> def function():
> """
>
> 4. At this point, CPU usage goes to 100%, I cannot type anything else
> into the buffer, but I can send a USR2 signal to end the 100% CPU
> usage, but the buffer has only partial syntax colouring.
OK, thanks. I can indeed reproduce this in Emacs 28.2, but not in
what soon will become Emacs 29.1. So I think this problem was already
solved between these two version.
> >I suspect this is already fixed in Emacs 29, but I cannot verify
> >without a file that reproduces the problem in Emacs 28.
>
> I will build an RPM package of emacs 29 and test that.
Thanks. I will wait for your confirmation before closing the bug as
fixed.
next prev parent reply other threads:[~2023-04-13 4:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-12 7:05 bug#62794: 28.2; jit-lock-function enters busy loop when open """ near top of large Python program Nick Urbanik
2023-04-12 15:39 ` Eli Zaretskii
2023-04-12 23:55 ` Nick Urbanik
2023-04-13 4:58 ` Eli Zaretskii [this message]
2023-04-13 5:25 ` Ruijie Yu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-13 5:39 ` Nick Urbanik
2023-04-13 6:01 ` Eli Zaretskii
2023-04-14 6:02 ` Nick Urbanik
2023-04-14 6:51 ` Eli Zaretskii
2023-04-14 2:49 ` Jim Porter
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=83jzyg5qfi.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=62794@debbugs.gnu.org \
--cc=nicku@nicku.org \
/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).