El 22/11/22 a las 0:40, Jeremy Bicha escribió:
On Mon, Nov 21, 2022 at 7:54 AM Santiago Vila <sanv...@debian.org> wrote:
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/
No. The most memory consuming webkit package in Debian allocates 6 GB or
7 GB of RAM during build. Compared with 237 GB, it's not similar.
Thanks.
