RFR: 8318302: ThreadCountLimit.java failed with "Native memory allocation (mprotect) failed to protect 16384 bytes for memory to guard stack pages" [v2]

[Thomas Stuefe]

On Tue, 27 Feb 2024 06:12:14 GMT, David Holmes <dholmes at openjdk.org> wrote:

> > So... if we reach the limit "max processes per user" we expect OOM, but if we reach vm.max_map_count, a fatal error is okay?
> 
> Yes. We can recover from `max processes per user` being reached, but we can't always recover from the max mappings being reached (there is actually just one fatal case when a new thread creates its own stack guard pages - there is no way to report a failure of that, so it is a fatal error).
> 
> In any case this PR is just about preventing this test from hitting a different limit to what it is trying to check.

Thank you for the clarification. The fix seems good.

-------------

PR Comment: https://git.openjdk.org/jdk/pull/17959#issuecomment-1965940912