| Field |
Value |
| Reporter |
@axeluhl |
| Assignee |
@axeluhl |
| Product |
Sailing Race Analytics |
| Component |
System Infrastructure |
| Version |
unspecified |
| Hardware |
All |
| OS |
All |
| Severity |
normal |
| Priority |
P3 |
| Created |
2026-03-18T00:02:06Z |
| Original Bug |
Bug 6221 |
ea11c93 should have removed the last Thread.stop() usage which would have been one of the show-stoppers for Java 26 compatibility. Other than that, we're mostly waiting for Java 26 to become available on Github Actions' setup-java action, then we could try this out.
Most relevant benefits would be in the area of G1GC performance improvements. In the long run, further improvements in Loom / virtual threads may be helpful, but that's a bigger story...
ea11c93 should have removed the last Thread.stop() usage which would have been one of the show-stoppers for Java 26 compatibility. Other than that, we're mostly waiting for Java 26 to become available on Github Actions' setup-java action, then we could try this out.
Most relevant benefits would be in the area of G1GC performance improvements. In the long run, further improvements in Loom / virtual threads may be helpful, but that's a bigger story...