return of 'Uninitialized object exists on backward branch' issue?
olagarde opened this issue · 9 comments
OSX, CENT7
JRE 1.7, 1.8, 1.10
last three releases of tesla core, tesla core lib, and poweredthingies (ending 6 Aug 18)
Probably something in my Java environment but I just can't find it.
- tried prior 3 releases in JRE 1.8 stack, same crash
- tried updating to latest 1.8 JRE, same crash
- tried 1.10 JRE compat STI for 1.8, same crash
- same with exactly one instance of JRE
- same with exactly one instance of JDK
- same with Oracle and Open JDK
- same with Oracle and Open Java runtime only
- same in fresh install on OSX and CENT7
- same in installs on base system and in fresh vbox images
For all failure cases the backtrace ends with javac bytecode validator claiming an invalid goto ref for poweredthingies pre-init bytecode generation, but this shouldn't happen if even one other user is successfully loading (which they are). I'm at a loss.
according to stack overflow: Upgrading from JDK 1.8.0_11 to 1.80_72 solved the problem for me.
. please try that.
Java Version: 1.8.0_11, Oracle Corporation
That's absolutely ancient.- Forge doesn't work with Java 10, no point even trying that.
- Minecraft 1.12.x was written for Java 8, no point trying it with Java 7.
No clue as to the cause, but those 3 points will atleast save you time debugging in future.
I'm dubious, Forge's ASM handlers Require Java 8 and earlier semantics, you might be able to get vanilla working on Java 10, or something not Forge, but forge itself is Java 8 or bust
Oh, I'm not bothered one way or the other, but, go let the forge boys know they're wasting their time redoing the loader, they'll be surely pleased you've saved them the time.
How about... Minecraft Forge for Minecraft 1.12 and up requires Java 8 and uses features of Java 8 that are not available on Java 7. It is also provably incompatible with Java 9 and later.
You are also running a positively ancient version of Java 8 - for the Windows versions Mojang/Microsoft is using Java 8u51 because of issues with some older Intel chipsets and I would not be surprised if Java 8u11 was a choice on OSX for similar reasons.
To that end... Some mods actually have issues with the versions of Java that ship with vanilla Minecraft. That actually appears to be the case here, as @faceofcat has stated that upgrading to, at least, 8u72 fixes the issue.
A solid recommendation, for everyone, is that they use the latest available version of Java 8 (I believe its somewhere around 8u151 for Windows and might be the same for all platforms) and ignore later Java versions (Java 9 and up) until both Vanilla and Forge support them.
Fixed, sort of. The fact that jdk versions outside 1.8 worked at all implies (requires, really) that there was a 1.8 dynlib orphaned ... somewhere. Otherwise the static forge prereq would fail, right? So I manually restored the /Library/.../JavaVM.frameworks/ and /System/.../Java/ from prior to the issue, rebooted, upgraded to 1.8.181, rebooted, and it started working again. So it probably was mixed versions, and definitely involved the base java loader dynlib (probably in /System/.../Java/ somewhere). Beyond that, who knows?