Integrated: 8371409: Wrong lock ordering between FullGCALot_lock and ThreadsLockThrottle_lock/MethodCompileQueue_lock
Coleen Phillimore
coleenp at openjdk.org
Thu Dec 4 22:37:02 UTC 2025
On Wed, 3 Dec 2025 12:59:34 GMT, Coleen Phillimore <coleenp at openjdk.org> wrote:
> This changes the rank of FullGCALot_lock to nosafepoint since it's taken when we want to do FullGCALot when we take safepoint lock so should always be a rank below that. This lock is very limited in what it does - it only protects some memory that we allocate at the bottom/beginning of the heap so that full gc with older collectors has to move stuff.
> Tested with tier1-4. I wrote a test case where I verified this change but the test case times out, so noreg-hard.
This pull request has now been integrated.
Changeset: 6db1c4f5
Author: Coleen Phillimore <coleenp at openjdk.org>
URL: https://git.openjdk.org/jdk/commit/6db1c4f5b93a1b7f7d9da36745dc433c9985a169
Stats: 3 lines in 2 files changed: 0 ins; 0 del; 3 mod
8371409: Wrong lock ordering between FullGCALot_lock and ThreadsLockThrottle_lock/MethodCompileQueue_lock
Reviewed-by: rehn, pchilanomate
-------------
PR: https://git.openjdk.org/jdk/pull/28633
More information about the hotspot-runtime-dev
mailing list