From: Eli Zaretskii <eliz@gnu.org>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: gregory@heytings.org, 57207@debbugs.gnu.org
Subject: bug#57207: 29.0.50; Fontification is slow after e7b5912b23 (Improvements to long lines handling)
Date: Mon, 15 Aug 2022 15:06:52 +0300 [thread overview]
Message-ID: <835yitiucj.fsf@gnu.org> (raw)
In-Reply-To: <87tu6d4txk.fsf@localhost> (message from Ihor Radchenko on Mon, 15 Aug 2022 19:39:35 +0800)
> Cc: 57207@debbugs.gnu.org
> From: Ihor Radchenko <yantar92@gmail.com>
> Date: Mon, 15 Aug 2022 19:39:35 +0800
>
> (b) Setting long-line-threshold to nil makes the slowdown disappear.
> Increasing long-line-threshold to 100000 made Emacs hang. I had to kill
> it using kill -9.
When it hangs, can you attach a debugger to it and try to figure out
where it loops? The instructions to do so are in etc/DEBUG, under "If
the symptom of the bug is that Emacs fails to respond". If that
procedure is more than you can afford, at least post the results of
"thread apply all bt" after attaching the debugger to a "hung" Emacs.
Thanks.
next prev parent reply other threads:[~2022-08-15 12:06 UTC|newest]
Thread overview: 103+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-14 15:55 bug#57207: 29.0.50; Fontification is slow after e7b5912b23 (Improvements to long lines handling) Ihor Radchenko
2022-08-14 16:08 ` Gregory Heytings
2022-08-14 17:31 ` Eli Zaretskii
2022-08-15 2:35 ` Eli Zaretskii
2022-08-15 9:03 ` Gregory Heytings
2022-08-15 11:41 ` Ihor Radchenko
2022-08-15 12:08 ` Eli Zaretskii
2022-08-16 10:47 ` Gregory Heytings
2022-08-16 11:55 ` Eli Zaretskii
2022-08-16 12:16 ` Ihor Radchenko
2022-08-16 12:24 ` Gregory Heytings
2022-08-16 12:39 ` Eli Zaretskii
2022-08-16 12:17 ` Gregory Heytings
2022-08-16 12:28 ` Ihor Radchenko
2022-08-16 12:43 ` Gregory Heytings
2022-08-20 16:50 ` Gregory Heytings
2022-08-21 3:25 ` Ihor Radchenko
2022-08-21 9:01 ` Gregory Heytings
2022-08-22 2:31 ` Ihor Radchenko
2022-08-22 14:09 ` Gregory Heytings
2022-08-22 15:45 ` Eli Zaretskii
2022-08-23 15:53 ` Gregory Heytings
2022-08-24 8:08 ` Ihor Radchenko
2022-08-24 8:26 ` Gregory Heytings
2022-10-10 8:09 ` Lars Ingebrigtsen
2022-10-10 12:03 ` Gregory Heytings
2022-10-11 0:25 ` Lars Ingebrigtsen
2022-12-08 10:05 ` Gregory Heytings
2022-08-16 12:50 ` Eli Zaretskii
2022-08-16 12:43 ` Eli Zaretskii
2022-08-15 11:39 ` Ihor Radchenko
2022-08-15 12:06 ` Eli Zaretskii [this message]
2022-08-15 14:12 ` Ihor Radchenko
2022-08-15 14:28 ` Eli Zaretskii
2022-08-15 17:08 ` Eli Zaretskii
2022-08-16 9:39 ` Ihor Radchenko
2022-08-16 12:33 ` Eli Zaretskii
2022-08-16 12:44 ` Gregory Heytings
2022-08-16 9:38 ` Ihor Radchenko
2022-08-14 16:24 ` Eli Zaretskii
2022-08-15 11:42 ` Ihor Radchenko
2022-08-15 11:53 ` Lars Ingebrigtsen
2022-08-15 12:10 ` Eli Zaretskii
2022-08-17 10:42 ` Lars Ingebrigtsen
2022-08-17 12:10 ` Eli Zaretskii
2022-08-17 12:36 ` Lars Ingebrigtsen
2022-08-17 13:27 ` Eli Zaretskii
2022-08-18 13:02 ` Lars Ingebrigtsen
2022-08-18 13:23 ` Eli Zaretskii
2022-08-18 13:33 ` Eli Zaretskii
2022-08-18 13:51 ` Lars Ingebrigtsen
2022-08-18 14:01 ` Lars Ingebrigtsen
2022-08-18 14:10 ` Eli Zaretskii
2022-08-18 14:13 ` Eli Zaretskii
2022-08-18 13:50 ` Lars Ingebrigtsen
2022-08-18 13:58 ` Eli Zaretskii
2022-08-18 14:02 ` Lars Ingebrigtsen
2022-08-18 14:13 ` Lars Ingebrigtsen
2022-08-18 14:14 ` Lars Ingebrigtsen
2022-08-18 14:32 ` Eli Zaretskii
2022-08-18 14:38 ` Lars Ingebrigtsen
2022-08-18 15:49 ` Eli Zaretskii
2022-08-19 12:02 ` Lars Ingebrigtsen
2022-08-19 12:22 ` Eli Zaretskii
2022-08-19 15:50 ` Lars Ingebrigtsen
2022-08-19 16:02 ` Lars Ingebrigtsen
2022-08-19 16:08 ` Lars Ingebrigtsen
2022-08-19 16:11 ` Eli Zaretskii
2022-08-19 16:16 ` Lars Ingebrigtsen
2022-08-19 17:21 ` Eli Zaretskii
2022-08-19 17:25 ` Lars Ingebrigtsen
2022-08-19 17:51 ` Eli Zaretskii
2022-08-20 9:15 ` Lars Ingebrigtsen
2022-08-20 9:29 ` Eli Zaretskii
2022-08-20 9:57 ` Lars Ingebrigtsen
2022-08-20 10:33 ` Eli Zaretskii
2022-08-20 17:14 ` Gregory Heytings
2022-08-20 17:26 ` Eli Zaretskii
2022-08-20 17:46 ` Gregory Heytings
2022-08-20 23:22 ` Gregory Heytings
2022-08-21 5:46 ` Eli Zaretskii
2022-08-21 11:43 ` Gregory Heytings
2022-08-21 12:02 ` Eli Zaretskii
2022-08-21 12:42 ` Gregory Heytings
2022-08-21 12:47 ` Lars Ingebrigtsen
2022-08-21 13:22 ` Gregory Heytings
2022-08-21 13:27 ` Lars Ingebrigtsen
2022-08-21 13:32 ` Gregory Heytings
2022-08-21 13:37 ` Lars Ingebrigtsen
2022-08-21 13:42 ` Eli Zaretskii
2022-08-21 13:38 ` Gregory Heytings
2022-08-21 13:39 ` Eli Zaretskii
2022-08-21 12:53 ` Eli Zaretskii
2022-08-21 13:18 ` Gregory Heytings
2022-08-21 13:24 ` Eli Zaretskii
2022-08-21 19:38 ` Gregory Heytings
2022-08-21 20:47 ` Lars Ingebrigtsen
2022-08-22 12:32 ` Eli Zaretskii
2022-08-22 14:00 ` Gregory Heytings
2022-08-21 12:08 ` Lars Ingebrigtsen
2022-08-19 16:20 ` Visuwesh
2022-08-19 17:22 ` Eli Zaretskii
2022-08-19 16:12 ` Eli Zaretskii
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=835yitiucj.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=57207@debbugs.gnu.org \
--cc=gregory@heytings.org \
--cc=yantar92@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).