NeoForge public release crash

I just moved over from the unstable releases of Sodium and Iris for NeoForge to the ones posted on CurseForge, and I'm getting crashes that tell me to update my graphics drivers(which I updated after the first crash). I'm not crashing when I have both of them turned off. I have attached the crash report.
95 Replies
dragon
dragon4w ago
I've tested a world without Iris, and it runs just fine. When I turn on Iris and use a shaderpack(Complementary Unbound in my case) I get a JVM crash. It works normally without a shaderpack turned on
JellySquid
JellySquid4w ago
@IMS this looks like an actual memory safety bug to me.
IMS
IMS4w ago
yes, I thought I fixed this earlier today in testing... there is no reliable reproduction as far as I can tlel
dragon
dragon4w ago
I can give you the settings for my memory allocation and whatever else you need
IMS
IMS4w ago
Is this crash reliably happening? and is it a new world?
dragon
dragon4w ago
yes it's happened no less than 6 times in the last 15 minutes
IMS
IMS4w ago
brand new world? hm
dragon
dragon4w ago
new world, or server
IMS
IMS4w ago
okay; would you be willing to test something for me?
dragon
dragon4w ago
sure thing
IMS
IMS4w ago
actually wait one second
IMS
IMS4w ago
I need you to cause the crash again with this version of Iris, and see if there are any messages immediately before the crash
dragon
dragon4w ago
I'm guessing you want me to place that in my mods folder and see if it works?
IMS
IMS4w ago
yep it will still crash; I just need to know if it gives a certain message before it crashes
Meeni
Meeni4w ago
doing that as well oh do you have a fabric build of the same
Want results from more Discord servers?
Add your server