[Webkit-unassigned] [Bug 248267] JSC init crashes WebKit with overcommit limit enabled

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=248267

Carlos Alberto Lopez Perez <clopez at igalia.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           See Also|                            |https://bugs.webkit.org/sho
                   |                            |w_bug.cgi?id=239957

--- Comment #10 from Carlos Alberto Lopez Perez <clopez at igalia.com> ---
(In reply to Paul van Tilburg from comment #0)
> With the update of WebKitGTK in Ubuntu (both 20.04LTS and 22.04LTS) of
> 2.36.8 to 2.38.2 on a system with a VM overcommit limit enabled, it now
> crashes the process on WebKit initialization via
> `webkit_web_context_new_ephemeral()` (or `webkit_web_context_new()`) without
> any error message.
> 
> I use the following overcommit configuration on 2 GiB and 4 GiB RAM systems:
> 
>   vm.overcommit_memory = 2
>   vm.overcommit_ratio = 80
> 

I'm a bit confused in respect to what those settings achieve.

After reading the kernel documentation <https://www.kernel.org/doc/Documentation/vm/overcommit-accounting> it looks to me that you are disabling overcommit, but then I also read this <https://unix.stackexchange.com/questions/348415/overcommit-memory-and-overcommit-ratio> and there is suggested another interpretation on those values (overcommit up to 80%).

Which one is the correct? What those parameters actually do?

Also.. what happens if you set vm.overcommit_memory = 0 ?

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20221125/1fa858e3/attachment.htm>