-
Enhancement
-
Resolution: Fixed
-
P4
-
17, 21, 23, 24
-
b05
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8341838 | 23.0.2 | William Kemper | P4 | Resolved | Fixed | b03 |
There are multiple places in Shenandoah where we take heap lock for potential free set diagnostics. There is no point in taking that lock if we do not report anything. We should at very least take the lock only when logging is actually needed.
See instances like:
```
{
ShenandoahHeapLocker locker(heap->lock());
heap->free_set()->log_status();
}
```
See instances like:
```
{
ShenandoahHeapLocker locker(heap->lock());
heap->free_set()->log_status();
}
```
- backported by
-
JDK-8341838 Shenandoah: Avoid taking lock for disabled free set logging
-
- Resolved
-
- relates to
-
JDK-8341554 Shenandoah: Missing heap lock when updating usage for soft ref policy
-
- Resolved
-
- links to
-
Commit
openjdk/jdk/c47a0e00
-
Commit(master)
openjdk/jdk23u/e2f4c7a1
-
Commit(master)
openjdk/shenandoah-jdk21u/8562abbe
-
Review
openjdk/jdk/19915
-
Review(master)
openjdk/jdk23u/129
-
Review(master)
openjdk/shenandoah-jdk21u/113
(3 links to)