Integrated: 8306965: osThread allocation failures should not abort the VM
David Holmes
dholmes at openjdk.org
Thu May 11 00:55:03 UTC 2023
On Tue, 9 May 2023 06:03:44 GMT, David Holmes <dholmes at openjdk.org> wrote:
> Trivial fix ... Currently OSThread allocation will abort the VM if there is not enough memory. While the fact we are exhausting C-heap means we are likely to abort for one reason or another, it isn't the role of thread starting to act as that trigger. So `new OSThread()` becomes `new (std::nothrow) OSThread()` and the existing null checks actually serve a purpose.
>
> Change was suggested by Kim Barrett - thanks.
>
> Testing:
> - tiers 1-3 sanity
> - GHA sanity
>
> Thanks
This pull request has now been integrated.
Changeset: 3cb606ef
Author: David Holmes <dholmes at openjdk.org>
URL: https://git.openjdk.org/jdk/commit/3cb606ef5b21b5d65cb97b459f30cdeacd035669
Stats: 8 lines in 4 files changed: 0 ins; 0 del; 8 mod
8306965: osThread allocation failures should not abort the VM
Reviewed-by: lfoltan
-------------
PR: https://git.openjdk.org/jdk/pull/13879
More information about the hotspot-runtime-dev
mailing list