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
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
@IMS this looks like an actual memory safety bug to me.
yes, I thought I fixed this earlier today in testing...
there is no reliable reproduction as far as I can tlel
I can give you the settings for my memory allocation and whatever else you need
Is this crash reliably happening?
and is it a new world?
yes
it's happened no less than 6 times in the last 15 minutes
brand new world?
hm
new world, or server
okay; would you be willing to test something for me?
sure thing
actually wait one second
I need you to cause the crash again with this version of Iris, and see if there are any messages immediately before the crash
I'm guessing you want me to place that in my mods folder and see if it works?
yep
it will still crash; I just need to know if it gives a certain message before it crashes
doing that as well
oh do you have a fabric build of the same
i guess
This what you're looking for?
no, I need the
latest.logHope that helps
cool
here's another test, now I'm trying to make the crashes stop
second verse same as the first? try it and send
latest.log if I crash?no, these ones won't have messages
just need to know if it crashes
hm, I wonder if it's related to ETF at all
lets see without
immediate crash, didn't even get a chance to move my camera lol
cool
I do have the console side errors if those help
I just need to know which, if any mods cause this
everything works without Iris, or if I turn off my shaderpacks
I'll dig, its not ETF or EBE
yes, but from how often it's happening to you it seems likely that another mod is triggering it to happen
I can't reliably fix it if I can't cause the bug
I can send you my mod list if you think it'll help
sure
and/or a modpack export
Here's the modpack export
ok, launching
it happens quickest on my server. it took a good long while in a fresh world
yeah I can't reproduce it...
hm.
crashes with nothing else but sodium and log4jconfig
so... it's not Iris?
or you mean Iris and those
Iris and those
oh
ok
you said trying a new world you suspect somehting with entities or whatnot?
just to test
here's a slight change
removed what I believe is the bad code
were you running a shaderpack?
potentially a stupid question
I'mma follow this post just to see the progress.
still crashing. it might just be old, developed worlds
yes
I can DM you the server IP and add you to the whitelist if you wanna test there
still crashing, but it doesnt crash in a new world
same
I am in xisumavoid base in hc7 wolrd /execute in minecraft:overworld run tp @s 1500.85 104.16 -233.18 64.16 0.60
test 2
there is absolutely no way this should be able to crash
famous last words
so far no crashes
looks like its working I'll keep it running a bit more
well, that's absolutely useless
because what I just did was remove all of the code to make sure that was the relevant spot
oh, I got this crash too
on fabric
lol sneaky
wait, the code did what exactly? lol
I'm getting crashes as soon as I load up NeoForge, Exit code 1
send log
it's likely unrelated
bear with me, i'm new to modding, how do you grab the crash log lol
How to get a log file:
Game logs can be found in the
logs sub-directory in .minecraft on clients, or the logs sub-folder of the server directory for servers. We're probably interested in the file named latest.log, which you can drag and drop into Discord.Tag requested by ims21
and
How to get crash reports:
Crash reports can be found in the
crash-reports sub-directory in .minecraft on clients, or the crash-reports sub-directory of the server directory for servers. We're probably interested in the most recent file, which you can drag and drop into Discord.Tag requested by ims21
should be the right ones
do you have Sodium?
it should have warned you
I have the alpha 3 from the unstable releases
i tried booting again with a fresh sodium install and get this report
you need beta 1
not alpha 3
ah
it can be found on Modrinth
eyyy, it worked.
in case you guys dont hear it enough, thanks for all you do
Marty's right y'all are awesome
You prolly will get some complaints from people running ATM10 till they update the modpack again
they did
0.38
Damn they did - literally between me updating my server and experiencing the crash and coming here to figure out if y'all had it as a bug
Dope!
neoforge not working with distant horizons mod
Not working?
:thonkwithshades:
It should Just Work™️, assuming no mod conflict.
you need to use the nightly build for DH 2.1.3 or wait for 2.2 to release
Ah right, thought you have the right DH version for Iris 1.8
i will test in 5 minutes wait for the news
i think its not working
Speaking of nightly, Distant Horizons now on 2.2.1-a-dev for their nightly builds.
game cant start
Do you have any other mods installed?
i have some mods
i delete all other mods but with distant horizons not working
Create a new issue post in #iris-issues, describe your issue and send relevant details like game logs and crash logs.
now i am checking 2.2.1 versions of distant horizon's i think its working
:ioa:
Did you pick version 2.1.2-a while testing?
both
2.1.2
Yeah Iris 1.8 will only work with Distant Horizons version 2.2 and above.
:ioa: