RFR: 8192647: GClocker induced GCs can starve threads requiring memory leading to OOME [v2]

David Holmes dholmes at openjdk.org
Thu Feb 6 06:41:21 UTC 2025


On Wed, 5 Feb 2025 19:39:30 GMT, Dean Long <dlong at openjdk.org> wrote:

>  I think we could go even further and eventually fold the JNI critical region into the existing safepoint mechanism.

@dean-long you seem to be forgetting why it was folded out in the first place. :) This was performance critical JNI code where the thread-state transitions were too heavyweight and expensive to use. So we keep the thread safepoint-safe (`_thread_in_native`) and have a way to tell the GC to pause whilst we are in these critical regions.

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

PR Comment: https://git.openjdk.org/jdk/pull/23367#issuecomment-2638962365


More information about the serviceability-dev mailing list