From: "Mattias Engdegård" <mattiase@acm.org>
To: Po Lu <luangruo@yahoo.com>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, 54698@debbugs.gnu.org
Subject: bug#54698: non-recursive GC marking [PATCH]
Date: Tue, 5 Apr 2022 13:11:44 +0200 [thread overview]
Message-ID: <75F6D65B-9CA1-4ECF-97BD-B934A84EB2CA@acm.org> (raw)
In-Reply-To: <87czhv53gd.fsf@yahoo.com>
5 apr. 2022 kl. 10.39 skrev Po Lu <luangruo@yahoo.com>:
> I think a failed xmalloc will also make Emacs prompt to "C-x s, then
> exit".
Yes, you're probably right. (Never seen it happen myself.)
> That code wasn't tested in an actual out-of-memory situation yet (it's
> too soon to consider this), but hopefully it will work. I think it
> works when running out of memory in general, because otherwise it
> wouldn't be what memory_full eventually asks the user to do.
Out-of-memory handling is difficult to do correctly and to test, especially on modern systems. You are right to make a reasonable effort at dealing with it but don't go overboard -- at some point effort is better spent on limiting user data loss in other ways (robust auto-save in particular).
> There's a lot of other
> low hanging fruit for optimization as well, but it's too early to work
> on those, since at present the garbage collector is not even working due
> to the recent changes that added a manually managed stack to the
> bytecode interpreter.
Very sorry about that (but Progress stops for nobody)!
In fact the new bytecode stack should provide more opportunities for efficient GC, but let's discuss that elsewhere.
> Thanks.
You're welcome.
next prev parent reply other threads:[~2022-04-05 11:11 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-03 18:40 bug#54698: non-recursive GC marking [PATCH] Mattias Engdegård
2022-04-04 11:01 ` Lars Ingebrigtsen
2022-04-04 11:16 ` Mattias Engdegård
2022-04-04 11:29 ` Lars Ingebrigtsen
2022-04-04 11:31 ` Lars Ingebrigtsen
2022-04-04 11:38 ` Eli Zaretskii
2022-04-04 11:57 ` Mattias Engdegård
2022-04-04 12:25 ` Eli Zaretskii
2022-04-04 17:18 ` Mattias Engdegård
2022-04-05 1:15 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-05 8:08 ` Mattias Engdegård
2022-04-05 8:39 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-05 11:11 ` Mattias Engdegård [this message]
2022-04-05 11:26 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-05 11:43 ` Eli Zaretskii
2022-04-05 12:31 ` Philipp Stephani
2022-04-05 13:12 ` Eli Zaretskii
2022-04-06 4:09 ` Richard Stallman
2022-04-06 5:48 ` Phil Sainty
2022-04-06 10:59 ` Eli Zaretskii
2022-04-06 12:05 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-06 12:23 ` Eli Zaretskii
2022-04-06 12:34 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-06 14:10 ` Eli Zaretskii
2022-04-06 12:52 ` Lars Ingebrigtsen
2022-04-08 4:24 ` Richard Stallman
2022-04-08 5:49 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-08 6:16 ` Eli Zaretskii
2022-04-08 7:41 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-08 11:15 ` Eli Zaretskii
2022-04-08 11:32 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-08 11:55 ` Lars Ingebrigtsen
2022-04-08 11:58 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-08 12:07 ` Lars Ingebrigtsen
2022-04-08 12:16 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-08 13:07 ` Lars Ingebrigtsen
2022-04-09 0:28 ` Phil Sainty
2022-04-08 12:13 ` Eli Zaretskii
2022-04-04 14:32 ` Andrea Corallo
2022-04-04 14:39 ` Mattias Engdegård
2022-04-04 15:44 ` Andrea Corallo
2022-04-04 16:04 ` Mattias Engdegård
2022-04-05 9:10 ` Andrea Corallo
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=75F6D65B-9CA1-4ECF-97BD-B934A84EB2CA@acm.org \
--to=mattiase@acm.org \
--cc=54698@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=luangruo@yahoo.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).