Client crash rendering Pylons 1.16 on OpenJ9 JVM
JennyLeeP opened this issue ยท 9 comments
Version Information
Forge version: 35.1.37
Botania version: botania:1.16.4-411
Further Information
https://gist.github.com/JennyLeeP/7d9b7aa10323d926923cb6b00d59c117
Steps to reproduce:
- First step : search "pylon" in JEI or load an area of the world with A pylon placed.
I usually only get a "p" typed before crashing. My friends on the same server do not get this crash. Only appears to happen on
my computer. - Second step : crash
- etc...
This render error happens with or without optifine insalled- mentioned because crash report shows I have optifine installed.
What I expected to happen: not crash - I.E render the item in JEI or the World.
What happened instead: crash
Windows 7? NVIDIA ? drivers are up to date.
Tried deleting everything and reinstalling MC instance, did not work.
for your enjoyment
https://gist.github.com/JennyLeeP/5e3928edf538de680c9f7a7b861dff72
I'm using a custom made modpack for 1.16.5 on 36.0.42.
I'm usually recommending my users to use Eclipse OpenJ9 as their JVM as this saves around 800MB of RAM usage.
However, I'm seeing reports of some people not having this problem anymore when switching to Hotspot. I'm currently asking them for more details and I'll be posting them later.
...I haven't noticed the OpenJ9 part... funny, because ModLauncher is supposed to literally stop the game from launching if you are using OpenJ9, see cpw.mods.modlauncher.ValidateLibraries#validate. The detection is currently broken on AdoptOpenJDK builds though.
Using OpenJ9 does cause some other issues, eg. Farmer's Delight crashes on launch on that JVM.
If you can provide crash logs on HotSpot I will be happy to investigate.
Everyone who encountered this, please post your crash logs and link the modpacks you use...
Weirdly enough, OpenJ9 seems to be working quite well with modlauncher itself (no errors/crashes), Forge just seems to not like the rendering part of some stuff, including botania pylons (even tho the stacktrace tells the errors line is the... start of a switch statement?).
I had an issue with some item rendering and shaders for items that didn't even use custom rendering, so that might also be the cause.
Anyways, since OpenJ9 is not supported by modlauncher, I'm guessing this won't be resolved unless exactly reproduced on hotspot. Thank you for your time and investigation on the issue.