After the launcher downloads 1.13.2's files, Minecraft doesn't launch, and it returns to the launcher. It only crashes when I load 1.13.2, every other version is fine.
I've looked as far into it as I could, but changing -Xss1G and other launch options didn't prove to be effective.
Linked issues
duplicates
Attachments
Comments
migrated
migrated
Updating Java doesn't appear to help, either. I will continue to look into this.
migrated
Maybe it has something to do with the removal of java DB in the 181 update
https://java.com/en/download/faq/release_changes.xml
I haven't tried installing what they suggest myself though because I don't really understand the language they use on the download page. https://db.apache.org/derby/releases/release-10.14.2.0.cgi
I'm not smart enough to figure this stuff out. All I know is that 1.13.1 works fine , then Java updated, and then 1.13.2 was released and isn't working on my computer either
migrated
Adding another launcher log just to see if anyone can see any differences.
migrated
Same result with the most recent snapshot.
[Mod] Neko
@unknown: What you attached are native logs. Please attach the launcher log (.minecraft/launcher_log.txt) here.
migrated
Sorry, usually not sure what to send, or where to find it.
[Mod] Neko
Thank you for your report!
However, this issue has been closed as a Duplicate of MC-137430.
It has been linked to this report. If you have additional information, please add it to the duplicated report.
Please search before reporting, as it's likely that one exists already.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki
migrated
After a friend and I sat down for a bit and tried solving this, editing our launch options proved futile (things like -Xmx1G -Xmn1000M -Xss1G, removing some things, etc.). The launcher shows nothing notably different. I'll attempt to reinstall Java, and if it gets to it, Minecraft as well.
Also, -Xss1G makes the launcher start the game, and then nothing happens. Not sure why.
migrated
Found a workaround! Adding -Xss320k -Xmx1G in your JVM Arguments works, but it may depend on your computer. Mess around with the two numbers until it works!
I have the same issue I tried everything so its not an issue from your side tho.