From: Eli Zaretskii <eliz@gnu.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: emacs-devel@gnu.org
Subject: Re: undo-auto--undoable-change infloop
Date: Tue, 26 Jul 2022 15:04:02 +0300 [thread overview]
Message-ID: <831qu8dqrx.fsf@gnu.org> (raw)
In-Reply-To: <87o7xc1qbh.fsf@web.de> (message from Michael Heerdegen on Tue, 26 Jul 2022 05:54:42 +0200)
> From: Michael Heerdegen <michael_heerdegen@web.de>
> Date: Tue, 26 Jul 2022 05:54:42 +0200
>
> does somebody have a guess what is happening here? After automatically
> replacing thousands of matches in a buffer with my el-search, I got a
> sluggish Emacs afterwards, after a short pause. Emacs consumed 100% of
> one CPU. It took me hours to find something, and it seems to be
> unrelated to my own code: `undo-auto--undoable-change'. It seems to
> recurse very deep, or to be called extremely often. I managed to
> produce a backtrace, see below. How is that recursion even possible -
> what could be going on?
I don't know what happened, but undo-auto--boundary-timer is invoked
10 sec after the timer is set. Perhaps this kind of problem can
happen when there are many undoable changes, and processing them takes
more than 10 sec?
next prev parent reply other threads:[~2022-07-26 12:04 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-26 3:54 undo-auto--undoable-change infloop Michael Heerdegen
2022-07-26 12:04 ` Eli Zaretskii [this message]
2022-07-27 3:52 ` Michael Heerdegen
2022-07-27 4:56 ` Michael Heerdegen
2022-07-27 11:20 ` Eli Zaretskii
2022-07-28 2:51 ` Michael Heerdegen
2022-07-28 3:10 ` Solved (was: undo-auto--undoable-change infloop) Michael Heerdegen
2022-07-28 5:49 ` Eli Zaretskii
2022-07-29 0:40 ` No, not solved " Michael Heerdegen
2022-07-29 3:44 ` No, not solved Michael Heerdegen
2022-07-29 4:12 ` Michael Heerdegen
2022-07-29 6:05 ` No, not solved (was: undo-auto--undoable-change infloop) Eli Zaretskii
2022-07-27 11:20 ` undo-auto--undoable-change infloop Eli Zaretskii
2022-07-27 17:06 ` Michael Heerdegen
2022-07-27 17:34 ` Eli Zaretskii
2022-07-28 2:45 ` Michael Heerdegen
2022-07-29 14:49 ` Stefan Monnier
2022-07-30 1:14 ` Michael Heerdegen
2022-07-30 4:14 ` Michael Heerdegen
2022-07-30 5:54 ` Eli Zaretskii
2022-07-30 7:23 ` Stefan Monnier
2022-07-31 4:05 ` Michael Heerdegen
2022-08-05 14:42 ` Stefan Monnier
2022-08-06 0:26 ` Michael Heerdegen
2022-08-09 4:02 ` Michael Heerdegen
2022-08-09 8:00 ` Stefan Monnier
2022-08-10 2:39 ` Michael Heerdegen
2022-09-21 13:28 ` Madhu
2022-09-21 14:17 ` timer.el API (was: undo-auto--undoable-change infloop) Stefan Monnier
2022-10-03 20:59 ` timer.el API Michael Heerdegen
2022-10-03 22:10 ` Stefan Monnier
2022-10-03 22:33 ` Michael Heerdegen
2022-10-07 20:50 ` undo-auto--undoable-change infloop Stefan Monnier
2022-10-09 2:32 ` Madhu
2022-10-09 4:23 ` Stefan Monnier
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=831qu8dqrx.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=michael_heerdegen@web.de \
/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).