bug#54698: non-recursive GC marking [PATCH]

[Mattias Engdegård]

4 apr. 2022 kl. 13.38 skrev Eli Zaretskii <eliz@gnu.org>:

> What happens with data that GC relocates, like when it relocates and
> compacts string data?  If the relocated data is allocated on the heap
> after the simulated stack, the original string data, which is now free
> memory, will be "trapped" behind the simulated stack, and 'free' will
> be unable to return it to the OS.  This could make the memory
> footprint of Emacs larger than it could be.

That effect is unlikely to be visible. I don't think a single (and not very 
big) allocation would contribute materially to heap fragmentation, given the 
amount of allocation being made all the time. (But prove me wrong!)

> Was this aspect considered and audited/tested?

Do you have a test case?