From: Eli Zaretskii <eliz@gnu.org>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: mitchellahren@gmail.com, 71644@debbugs.gnu.org
Subject: bug#71644: 30.0.50; Severe slowdown in larger files with markers beginning in emacs 29+
Date: Sat, 22 Jun 2024 17:12:47 +0300 [thread overview]
Message-ID: <86iky1gj6o.fsf@gnu.org> (raw)
In-Reply-To: <87zfrdgk3f.fsf@localhost> (message from Ihor Radchenko on Sat, 22 Jun 2024 13:53:08 +0000)
> Cc: 71644@debbugs.gnu.org
> From: Ihor Radchenko <yantar92@posteo.net>
> Date: Sat, 22 Jun 2024 13:53:08 +0000
>
> Mitchell <mitchellahren@gmail.com> writes:
>
> > Here are the steps to reproduce the issue:
> > ...
>
> For the record, I am able to reproduce the problem using the latest
> Emacs master.
>
> And the problem does disappear with my patch that affects the marker
> loop in src/marker.c (buf_bytepos_to_charpos)
>
> So, markers appear to be the culprit on my system.
Not the markers, but conversion of character positions to buffer
positions. Which uses markers, but that's an implementation detail...
next prev parent reply other threads:[~2024-06-22 14:12 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-19 5:25 bug#71644: 30.0.50; Severe slowdown in larger files with markers beginning in emacs 29+ Mitchell
2024-06-19 12:56 ` Eli Zaretskii
2024-06-20 13:49 ` Ihor Radchenko
2024-06-20 16:11 ` Eli Zaretskii
2024-06-20 16:24 ` Eli Zaretskii
2024-06-20 18:57 ` Mitchell
2024-06-20 19:04 ` Eli Zaretskii
2024-06-21 2:46 ` Mitchell
2024-06-21 6:19 ` Ihor Radchenko
2024-06-21 20:53 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-22 5:23 ` Gerd Möllmann
2024-06-22 14:10 ` Ihor Radchenko
2024-06-22 15:52 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-25 3:07 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-25 4:00 ` Eli Zaretskii
2024-06-25 9:30 ` Ihor Radchenko
2024-06-25 13:44 ` Eli Zaretskii
2024-06-25 13:50 ` Ihor Radchenko
2024-06-25 13:57 ` Eli Zaretskii
2024-06-25 14:25 ` Ihor Radchenko
2024-06-26 3:53 ` Mitchell
2024-06-26 12:41 ` Eli Zaretskii
2024-06-25 20:54 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-26 11:41 ` Eli Zaretskii
2024-06-26 12:35 ` Ihor Radchenko
2024-06-26 13:30 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-26 13:49 ` Ihor Radchenko
2024-06-26 14:08 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-29 21:27 ` Mitchell
2024-06-25 21:02 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-21 6:48 ` Eli Zaretskii
2024-06-21 21:06 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-22 6:57 ` Eli Zaretskii
2024-06-22 18:03 ` Mitchell
2024-06-22 18:17 ` Eli Zaretskii
2024-06-24 7:09 ` Mitchell
2024-06-24 12:38 ` Eli Zaretskii
2024-06-25 3:08 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-22 13:53 ` Ihor Radchenko
2024-06-22 14:12 ` Eli Zaretskii [this message]
2024-06-22 14:15 ` Eli Zaretskii
2024-06-22 15:09 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=86iky1gj6o.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=71644@debbugs.gnu.org \
--cc=mitchellahren@gmail.com \
--cc=yantar92@posteo.net \
/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).