According to other community reports, LWJGL, the rendering library used by Minecraft, switches its MemoryUtil back-end from Unsafe to FFM on Java 25. However, JIT in Java 25 seems can’t works well with FFM back-end, and causing performance issue.
So theoretically, if you try to launch older version with Java 25, and this issue also appears, then we can confirm this issue is related to the back-end switch.
JerryHan3
According to other community reports, LWJGL, the rendering library used by Minecraft, switches its
MemoryUtilback-end from Unsafe to FFM on Java 25. However, JIT in Java 25 seems can’t works well with FFM back-end, and causing performance issue.So theoretically, if you try to launch older version with Java 25, and this issue also appears, then we can confirm this issue is related to the back-end switch.
Developers of LWJGL and other community members are still investigating this issue on Github: https://github.com/LWJGL/lwjgl3/issues/1111