> Okay, my bad, I should be more specific. What matters here is how much memory is allocated for single Lua heap, not how much memory consumes some program that embeds Lua.
See
https://www.lua.org/bugs.html#5.3.4-2 . Even if that was reported by me with an artificial repro case, it originally hit a customer installation, with a table holding some fat values, all in one Lua state, consuming quite a few gigs before it went down.
Cheers,
V.
