From: Eli Zaretskii <eliz@gnu.org>
To: "Mattias Engdegård" <mattiase@acm.org>
Cc: telegraph@gmx.net, 53809@debbugs.gnu.org
Subject: bug#53809: 29.0.50; fatal error: assertion failed: string_immovable_p (bytestr)
Date: Mon, 07 Feb 2022 21:45:45 +0200 [thread overview]
Message-ID: <831r0exxxy.fsf@gnu.org> (raw)
In-Reply-To: <9A1F0B52-CB38-4BB9-934F-37FB28ABCBBC@acm.org> (message from Mattias Engdegård on Mon, 7 Feb 2022 20:09:01 +0100)
> From: Mattias Engdegård <mattiase@acm.org>
> Date: Mon, 7 Feb 2022 20:09:01 +0100
> Cc: telegraph@gmx.net, 53809@debbugs.gnu.org
>
> 7 feb. 2022 kl. 19.52 skrev Eli Zaretskii <eliz@gnu.org>:
>
> > Does this mean that Emacs will now be even less willing to return
> > memory to the OS, because the bytecode strings cannot be moved by GC?
>
> Not to any significant degree
How do you know? Was this measured?
> but it is of course a legitimate concern. Bytecode strings are rarely freed at all; they are typically loaded once and remain until Emacs terminates. Dynamic bytecode generation and replacement is comparatively rare.
I'm not talking about GC that frees unused string, I'm talking about
GC that moves string data to compact strings that aren't freed.
> Strings are allocated in either of two heaps: one for short strings (≤1024 bytes) and another for large ones. Only the short string heap is compacted, so all the pinning mechanism does is to use the large-string heap for all bytecode strings.
Which is exactly my bother.
prev parent reply other threads:[~2022-02-07 19:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-05 22:50 bug#53809: 29.0.50; fatal error: assertion failed: string_immovable_p (bytestr) Gregor Zattler
2022-02-06 7:38 ` Eli Zaretskii
2022-02-06 23:44 ` Gregor Zattler
2022-02-07 13:49 ` Eli Zaretskii
2022-02-07 14:12 ` Gregor Zattler
2022-02-07 14:30 ` Eli Zaretskii
2022-02-07 15:01 ` Mattias Engdegård
2022-02-07 15:19 ` Gregor Zattler
2022-02-07 16:48 ` Mattias Engdegård
2022-02-07 18:07 ` Gregor Zattler
2022-02-08 20:50 ` Mattias Engdegård
2022-02-07 18:52 ` Eli Zaretskii
2022-02-07 19:09 ` Mattias Engdegård
2022-02-07 19:45 ` Eli Zaretskii [this message]
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=831r0exxxy.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=53809@debbugs.gnu.org \
--cc=mattiase@acm.org \
--cc=telegraph@gmx.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).