unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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: Wed, 12 Apr 2023 18:39:05 +0300	[thread overview]
Message-ID: <83a5zd6rfq.fsf@gnu.org> (raw)
In-Reply-To: <ZDZYKbRMc0xlMTNw@nicku.org> (message from Nick Urbanik on Wed, 12 Apr 2023 17:05:13 +1000)

> Date: Wed, 12 Apr 2023 17:05:13 +1000
> From: Nick Urbanik <nicku@nicku.org>
> 
> 
> 
> 1. Start emacs with emacs -Q
> 2. Read in a large python file (3100 lines long, more than 10,000
>     characters)

Thanks.

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.

> 3. Near the top, type the following:
> 
> def function():
>     """
> 
> 4. No further input is accepted.
> 5. CPU usage is 100% as shown in /usr/bin/top
> 6. type kill -USR2 {process_id_of_emacs-Q}
>     and the emacs window closes.
> 7. From my emacs started without '-Q', when I type
>     killall -USR2 emacs
>     I see:
> Debugger entered--entering a function:

I suspect this is already fixed in Emacs 29, but I cannot verify
without a file that reproduces the problem in Emacs 28.





  reply	other threads:[~2023-04-12 15:39 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 [this message]
2023-04-12 23:55   ` Nick Urbanik
2023-04-13  4:58     ` Eli Zaretskii
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=83a5zd6rfq.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).