Crash on startup, Java fails to start
Smellslikeoranges opened this issue · 12 comments
I'm not entirely sure what is the causing the problem, but as soon as the startup process starts to register Fluidlogging API, LaunchWrapper reports that it's unable to launch.
I'm using version 1.6.2
According to the crash log, it would seem you have two instances of fluidlogged api installed (along with some other duplicate mods). Try removing those and let me know if that helps.
Actually, one of those two instances of fluidlogged api (1.5.2) was disabled, I was testing earlier to see if the crash was specific to the current version. It wasn't I'm afraid.
The other duplicate mods are also disabled.
does this fix your issue? The next version of this mod is planned to have built-in vanilla tile entity support, but that won't be out for a while.
Thanks for the attempted fix. It got much farther through the start-up process, but it did still crash when it was registering the "BlockRailBase" it looks like.
It crashed again, a little bit earlier this time, I can't really identify why from the log.
how about this? I did this in earlier versions, but if I recall correctly, this gave someone else problems so I changed it.
extract me.zip third time's the charm I hope lol. If this doesn't work, then I'll work on this tomorrow, getting late here
Sadly, it did crash again. Oh well, we tried. Thanks again for all your help.
At any rate, I'll still post the log for later reference: https://paste.ee/p/NwHYb
Have a good night!
this simply removes the transformation that seems to be causing all this. If it still doesn't work, then it's possible the issues are caused by something else another mod is doing.
Having just tried it, it did crash again, so I'm definitely in agreement that a separate mod is probably causing it.
Sorry for all the trouble, I wish I had a good way of telling which one is acting problematic. :/
If I were you, I'd test to see if the crash occurs without any instance of fluidlogged api installed, just to be truly sure the crash doesn't relate to it (if you haven't already). There are two things outside the mod that catch my eye. The first thing is something called "Meson ASM" at line 988 in the crash log. It seems to cause the crash. I tried looking up the mod, but found nothing, do you know what it is? The second thing is that you're using optifine E3, which is made for forge v2795 Try updating optifine to G5 and see if that does anything.
Edit: G5 is made for forge v2847. So even if updating optifine doesn't help, backporting forge may be worth doing. I know for myself I prefer working with forge v2847, since the versions that come after mess up how asm is handled in a dev workspace. The forge version alone may even be causing the crash with some other mod that's made for the earlier versions ¯_(ツ)_/¯