Bug#1024532: gjs allocates 237 GB of RAM during build (!)

[Jeremy Bicha]

On Mon, Nov 21, 2022 at 7:54 AM Santiago Vila <sanvila at debian.org> wrote:
> El 21/11/22 a las 11:20, Simon McVittie escribió:
> > I think you might accidentally be measuring how much it *can* allocate
> > if given the opportunity, as opposed to how much it strictly *needs*
> > to allocate?
>
> Not exactly. As explained, I am intentionally measuring the allocated
> memory as a completely safe upper bound for the required memory, and I
> am aware that they are not the same. Nevertheless, I try to report
> anomalies like this one when I find them.

Another example is webkitgtk. It uses overcommit as a security feature
codenamed Gigacage. The webkitgtk maintainers would close this kind of
bug as NOTABUG. Perhaps, gjs is doing something similar.

https://blogs.gnome.org/mcatanzaro/2018/11/02/on-webkit-build-options-also-how-to-accidentally-disable-important-security-features/

Thank you,
Jeremy Bicha