From: Eli Zaretskii <eliz@gnu.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: 46908@debbugs.gnu.org, casouri@gmail.com
Subject: bug#46908: 28.0.50; Dozens of spurious markers in buffer-undo-list
Date: Sat, 06 Mar 2021 09:48:35 +0200 [thread overview]
Message-ID: <83y2f0wwmk.fsf@gnu.org> (raw)
In-Reply-To: <87y2f1m7ez.fsf@web.de> (message from Michael Heerdegen on Sat, 06 Mar 2021 01:51:00 +0100)
> From: Michael Heerdegen <michael_heerdegen@web.de>
> Date: Sat, 06 Mar 2021 01:51:00 +0100
> Cc: 46908@debbugs.gnu.org, Yuan Fu <casouri@gmail.com>
>
> My question is what amount of that is pathological. A lot of code
> creates markers "on the fly", a lot, e.g. jit-lock or yank (push-mark)
> or display-buffer. When undo is performed before gc is run, they end in
> buffer-undo-list.
>
> Does making a marker point to nil with `set-marker' then make it
> suitable for garbage collection? I guess not.
GC compacts the buffer's undo-list, and that is supposed to remove
those entries. Doesn't it?
next prev parent reply other threads:[~2021-03-06 7:48 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-03 22:45 bug#46908: 28.0.50; Dozens of spurious markers in buffer-undo-list Michael Heerdegen
2021-03-04 8:35 ` martin rudalics
2021-03-04 16:40 ` Michael Heerdegen
2021-03-04 17:20 ` martin rudalics
2021-03-04 18:35 ` Michael Heerdegen
2021-03-05 9:11 ` martin rudalics
2021-03-05 9:50 ` martin rudalics
2021-03-06 0:51 ` Michael Heerdegen
2021-03-06 7:48 ` Eli Zaretskii [this message]
2021-03-07 2:45 ` Michael Heerdegen
2021-03-06 8:40 ` martin rudalics
2021-03-07 2:40 ` Michael Heerdegen
2021-03-08 4:00 ` Michael Heerdegen
2021-03-08 8:26 ` martin rudalics
2021-03-09 2:04 ` Michael Heerdegen
2021-03-09 2:20 ` Michael Heerdegen
2022-06-20 0:04 ` Lars Ingebrigtsen
2022-06-20 13:56 ` Michael Heerdegen
2021-03-09 8:10 ` martin rudalics
2021-03-10 2:17 ` Michael Heerdegen
2021-03-10 5:49 ` Richard Stallman
2021-03-09 6:19 ` Richard Stallman
2021-03-10 2:22 ` Michael Heerdegen
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=83y2f0wwmk.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=46908@debbugs.gnu.org \
--cc=casouri@gmail.com \
--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).