For Whatever Reason, If I try Play 1.18, The Game Crashes and Doesnt Even Open, it just Crashes Immediately
Linked issues
duplicates 1
Attachments
Comments 64
Please attach the crash report or log. The crash report is a text file located in the [.minecraft|https://minecrafthopper.net/help/finding-minecraft-data-folder/]/crash-reports folder named crash-date-client.txt. If not available attach the complete launcher_log.txt file.
Im having this same issue, I also play on a Max OS 10.11.6, and I also had the same the launcher bug problem as well.
The application did not create a crash report. I have uploaded the launcher log file instead. Good luck!
For once i actually am able to find a bug report for an issue i’m having without having to post my own first, i will add that this was also happening for me on mac for the 1.18 pre-releases alongside the full release
Same issue. Macbook Pro. macOS 10.11.6. MC 1.18. No crash report created. Will look for the launcher log.
I have the same situation, also on a macOS 10.11.6
Same situation for me
Yeah, same for me. Mac OS X 10.11.6. Updating to 1.18 had to download about 60~ish mb. Downloading hung for ages (15- 20 mins) around 40mb. I have a good internet connection. (no, not Great but good... or good enough that this was slow) Creeped very slowly to full download. Then it had to install. Fine. This is expected. 'Finalisation' said it estimated to take about 1 minute... then hung again and I had to just wait and then crashed after about 20 mins. Exit Code: 0
[media]I shut everything down and restarted computer. I started Launcher and got approx 50% through 'Preparing' and then crashes. Same vague error message. Exit Code: 0 after many of us have experienced vague error messages from the most recent launcher bug 19840 This is particularly frustrating. It would be good to include a more specific error message so we can report it easyier and devs can pinpoint problems. ERROR GAME CRASHED... unexpected, Exit... ZERO EXIT CODES...
This is so vague that BOTS literally turned off the ticket for a bug last time around... and probably will again with this vague crash.
Jess Edward suggested attaching the crash report for this bug with todays date... I've looked in the crash log folder... but alas todays date isn't in there. So Jess also suggests adding the launcher_log.txt, which I've attached. But I can't see anything there that points towards a crash.
In addition to this in-game or in-Launcher crash it also triggered another crash simultaniously which I couldn't screen capture via the usual method and have taken a photo of instead
[media]Clicking on Report option brings up this report to Apple box. Probably not helpful for Apple. I doubt they care.
[media]The contents of the 'Problem Details and System Configuration' box probably give some of you more information about my machine than I should be sharing but... to bad I'm upgrading to a different machine and OS soon anyway but want to provide some assistance to some peeps who are battling it out on some older tech like me currently... anyway... the full log is in the 'send to apple. txt' I've also attached.
[media]
Do you have Java 16? Minecraft Java Edition 1.17+ requires Java 16. You can check which version you have by opening the terminal app, and typing in 'java -version' to check your version. If you don't, download Java 16 from Oracle or another trusted source.
Minecraft bundles its own JRE; that shouldn't be relevant.
Sanjiv: How odd....I had been running Minecraft 1.17 perfectly fine while my PC has Java 8.........infact when at the java site it has Java 8.331 as the current downloadable version and only offers java 8.
Found out that this is a Java oracle bug. Basically, when I download Java 17, it downloads correctly. However, when I check the version of Java on my Mac (10.11.6) it shows and error and says the Java quit unexpectedly. I don’t have any clue if mojang can fix this. I really think this is a Java Oracle bug
Can confirm this has been happening to me since Pre Release 2, when the change to Java 17 was made. Works fine for PR1. Mojang, please fix this. During the development of 1.18 there have been ever so many bugs for Mac systems. New updates are all well and good but make them accessible! Please!
See MC-242661 "Fatal Process crashed with exit code 11"
Ugh, I see the launcher log is provided by another. Likely the same issue you're all having.
Jess Edward, this does not duplicate that. This is exit code 0, not 11. May be a related issue, but not the same issue. Thanks for connecting the issues though as they are possibly related to one another with perhaps a common source of the problem.
Its in the launcher log. That's why I asked for it.
Just adding a copy of my Launcher Log renamed to include my initials. I thought I had added my own copy in my previous post but when I opened the one that is linked to my comment the Username in the File path shows that it is obviously not mine but Scott Redingers.
Same here, I'm attaching my launcher logs and the OS java crash log. What we know so far is this:
This seems to only happen on mac OSX 10.11.6 (El Capitan).
It started with 1.18-pre2 so, if I got that right, when Minecraft switched from java 16 to java 17.
It does not depends on what version of java is installed since Minecraft uses its own packed runtime.
It does not depends on what's inside the minecraft folder or an incorrect installation since it still happens in freshly reinstalled Minecraft with emptied minecraft folder.
It happens so early that no game logs are produced.
To some of us it's also accompanied by a "java quit unexpectedly" OSX warning message.
Sometimes the launcher crashes too.
Thank you @Eugenio Scalfi.
I would like to add another fact.... If I switch the game back to 1.17.1, there are no errors and the game opens normally.
Unfortunately, this doesn't help me enjoy Minecraft since I play on Realms with my son and Realms doesn't allow any other versions except the newest.
When I open 1.18, it crashes like everybody elses here ...but I don't have the Java crash message.
I am on Mac 10.11.6 with Java 8.
That's because the bug was introduced in snapshot 1.18-pre2 (can everyone confirm this?), so every version up until 1.18-pre1 works fine
Well, I'm not sure about it being a Java 17 issue. I had previously inistalled Java 17 because I couldn't get amidst 4-7 to work on my computer and still can't but the forums for that suggested 16 which didn't work so I also tried 17 also no luck but I could still play minecraft 1.17.1. I still can play 1.17.1 but 1.18 is where I get the game crashing
However, I should also mention that like other users have experienced I am getting a Java crash window as wellas the in game crash screen error. So maybe I'm wrong about the not Java bit.
Of course it has to do with java since the game run on that, but it does not have to do with the version of java that is currently installed on the computer because minecraft comes bundled with it's own java runtime (java 17 for mincraft 1.18-pre2 and up, java 16 for previous versions).
This is also a problem for me. I'm on Mac OS 10.11.6 El Capitan. Can't play on 1.18 but it works just fine on 1.17 and 1.17.1.
Mac 10.11.6.
1.18 crashed when attempting to open.
Just fixed the previous launcher issue last week to have it taken away this week. Please add another to the list of so this gets looked at faster.
I'm also getting the game crashed, exit code: 0 message on Mac OS 10.11.6, however I haven't received any Java crash messages.
I am having this problem on a MacBookPro and on an iMac both running 10.11.6 (El Capitan) as well.
I'm having the exact same issue also playing on mac OS 10.11.6.
I too am having the same issue, just after they fixed the login bug recently and now this. im also on mac OS 10.11.16 so sad cant even play anymore too many issues
[Info: 2021-12-05 22:06:12.622493: NetQueue.cpp(157)] NetQueue: Setting up.
[Info: 2021-12-05 22:06:12.622744: NetQueue.cpp(575)] NetQueue: worker thread started.
[Info: 2021-12-05 22:06:12.622819: mainOSX.cpp.mm(54)] Running launcher bootstrap (version 1036)
[Error: 2021-12-05 22:06:12.631735: localization.cpp(45)] No locale matching [en-(null).json] found.
[Error: 2021-12-05 22:06:12.631777: localization.cpp(110)] No translation found for "Unable to download <game>. Please try again later."
[Error: 2021-12-05 22:06:12.631800: localization.cpp(110)] No translation found for "Unable to download the <game> Native Launcher."
[Error: 2021-12-05 22:06:12.631819: localization.cpp(110)] No translation found for "Unable to update the <game> Game Launcher."
[Error: 2021-12-05 22:06:12.631836: localization.cpp(110)] No translation found for "Unable to download the <game> Runtime Environment."
[Error: 2021-12-05 22:06:12.631852: localization.cpp(110)] No translation found for "Unable to update the <game> Game Launcher."
[Error: 2021-12-05 22:06:12.631868: localization.cpp(110)] No translation found for "Unable to update the <game> Runtime Environment."
[Error: 2021-12-05 22:06:12.631884: localization.cpp(110)] No translation found for "Unable to update the <game> Native Launcher."
[Error: 2021-12-05 22:06:12.631901: localization.cpp(110)] No translation found for "Unable to relaunch the Minecraft bootstrap."
[Error: 2021-12-05 22:06:12.631917: localization.cpp(110)] No translation found for "Unable to start the <game> Runtime Environment. This is most likely caused by a corruption. Please try to reinstall <game>."
[Error: 2021-12-05 22:06:12.631934: localization.cpp(110)] No translation found for "Unable to start <game>, if you are running from a dmg, please drag to Applications and try again."[Info: 2021-12-05 22:06:12.622493: NetQueue.cpp(157)] NetQueue: Setting up.
[Info: 2021-12-05 22:06:12.622744: NetQueue.cpp(575)] NetQueue: worker thread started.
[Info: 2021-12-05 22:06:12.622819: mainOSX.cpp.mm(54)] Running launcher bootstrap (version 1036)
[Error: 2021-12-05 22:06:12.631735: localization.cpp(45)] No locale matching [en-(null).json] found.
[Error: 2021-12-05 22:06:12.631777: localization.cpp(110)] No translation found for "Unable to download <game>. Please try again later."
[Error: 2021-12-05 22:06:12.631800: localization.cpp(110)] No translation found for "Unable to download the <game> Native Launcher."
[Error: 2021-12-05 22:06:12.631819: localization.cpp(110)] No translation found for "Unable to update the <game> Game Launcher."
[Error: 2021-12-05 22:06:12.631836: localization.cpp(110)] No translation found for "Unable to download the <game> Runtime Environment."
[Error: 2021-12-05 22:06:12.631852: localization.cpp(110)] No translation found for "Unable to update the <game> Game Launcher."
[Error: 2021-12-05 22:06:12.631868: localization.cpp(110)] No translation found for "Unable to update the <game> Runtime Environment."
[Error: 2021-12-05 22:06:12.631884: localization.cpp(110)] No translation found for "Unable to update the <game> Native Launcher."
[Error: 2021-12-05 22:06:12.631901: localization.cpp(110)] No translation found for "Unable to relaunch the Minecraft bootstrap."
[Error: 2021-12-05 22:06:12.631917: localization.cpp(110)] No translation found for "Unable to start the <game> Runtime Environment. This is most likely caused by a corruption. Please try to reinstall <game>."
[Error: 2021-12-05 22:06:12.631934: localization.cpp(110)] No translation found for "Unable to start <game>, if you are running from a dmg, please drag to Applications and try again."
@Mojang the "Affects Versions" is noted as (macOS - 10.9 only) but most of the reports here are using 10.11.6. If I didn't add this before, my mac (10.11.6) is using Java 8.
literally every single commenter says they're on 10.11.6, even in all the duplicate tickets, why putting 10.9? it doesn't make any sense, do they even read these?
This is so frustrating, ever since Microsoft took over there is just nothing but trouble. I've been playing Minecraft for over a decade and I never had a single issue until I migrated my account three months ago.
Problem is on 10.11.6 - see my report and info under MCL-20784. Appears to be related to the embedded "beta" Java 17.0.1.
Hey I'm not an expert or anything, I have next to 0 knowledge on java or mac os operating systems. I mean I just wanna be able to play realms lol, but I just thought I'd share. I believe the problem lies in our operating system 10.11.6 and the java it can run reading over David's post under MCL 20784 a commenter under the name Kiara stated -
"I emailed them and they told me they are fixing it. So i think we’ll be good."
This may be nothing but for now it's a glimmer of hope because I think I speak for the majority of us in saying, we don't want to have to upgrade to a new system just to play because some of us may not be able to update our systems pass 10.11.6 meaning we'll have to buy new systems entirely.
Once Microsoft got their hands on this I too got worried. They tend to drop support for older versions with updates FORCING you to update to their latest software. I am running Win 8.1 on a PC. From several help replies I have been given trouble shooting for Win 10/11 even though I specifically told them I was running Win 8.1.......that's not very promising.....LOL
Update on my testing posted in MCL-20784:
My early-2008 8-core Mac Pro is only supported up to 10.11.6 (El Capitan). However, there is a 3rd-party patch available that allows 10.13 (High Sierra) to install on some of these early machines. I Installed 10.13 on an external drive, and the machine boots and apparently runs normally, except for an incompatibility with the wifi card. Under 10.13, I launched /minecraft/runtime/java-runtime-beta/mac-os/java-runtime-beta/jre.bundle/Contents/Home/bin/java, which is the bundled Java 17.0.1. It executed and displayed the help file in the terminal, which did not happen under 10.11.6. I then started the Minecraft launcher, signed in, selected "Latest Release 1.18" and clicked the play button. The progress bar slowly went to 100%, and then the Mojang screen opened. The game runs fine - I can now play 1.18! I'm even getting slightly higher FPS than before. There was an incident where the FPS dropped to near zero, but I doubt that is related. It cleared when I exited to the main menu and reloaded my save.
Again, as a non-expert, this problem seems to stem from an incompatibility between 10.11.6 and Java 17.0.1. Not sure if it is within Mojang's ability to remedy, other than perhaps pressing Oracle for a Java update. On the bright side, there is a viable workaround than is essentially free. Note that if you need to use the built-in wifi, you'll have to get a different card or use an external wifi adapter. Lastly, it worked for me but I make no guarantees of any sort. I installed High Sierra on an external drive, but I have not upgraded my 10.11.6 partition yet. Research thoroughly and proceed with caution.
There are some options to install newer OSX versions on officially unsupported hardware (Hackintosh for example) but those are far from ideal, OSes tends to become heavier and more resource-consuming over time because of newer hardware permitting so, old hardware becomes unsupported for a reason, newer versions gets older hardware slower and more unresponding, if not straight non-functioning because of driver incompatibility. Mojang must either address the bug or officially drop support for 10.11.6 so that people can move on (preferably the former). Nice work by the way
Has anyone tried using an older version of Java 17? I realize there's not much wiggle room there because it's so early into Java 17's lifespan, but even a beta version might make the difference. Yes, you can manually tell Minecraft which version of Java to run instead of the bundled version.
The problem persists for my two 10.11.6 Macs with the same crash/error messages.
same thing is happening for me. First time i tried to load 18 and 18.1 i got the error message then the launcher froze and couldn't quit so had to restart the whole system. Now when i try it just crashes and quits while "preparing". Also no crash reports seem to be being made, i've checked the files. Hopefully we get a fix soon
[media]
also for some reason, a bot merged my report to a completely different ticket than this one with only 6 reports on it. Even though this is the issue i'm dealing with
Its now 1.18.1 but there hasn't been any updates at all. I was only told they were working on but haven't heard anything since November. Any updates anyone? I'm on Mac 10.11.6
Good morning,
Any word of Mojang working on this crash? i dont think i have seen any progress on this since day one of 1.18.
Thank you
I emailed them once again and they said they are still working on it. Its strange but they also said they tracking the problem on ticket MCL-19840. They said the both bugs are leading to the same bug.
thanks for the info, I was following that issue first then when it was corrected i unfollowed it. But now i will add my name back to that list as well.
Yeah, no progress for the same issues with Win 8.1 as well, well other than one Mod suggesting upgrading to Win 10 to see if that "helps". He even included links to upgrade to Win 10 or 11.
Damn bruh, minecraft wasn't opening at all for three weeks and now 1.18 doesn't work :/
El Capitan 10.11.6 user here. Having the same issue, this bug has been going on for a long time now. And I’ve tried pretty much everything I could to fix it but nothing does. Starting to wonder if this might be unfixable as my machine is getting older (late 2012 iMac) I would just appreciate more transparency as to where this issue is going, if being looked at at all. New update is incredible, its a shame some players are being left out because of that bug. If support is no longer possible for El Capitan, just let us know please.
Can't install 1.18 to resolve Log4 vulnerability 😞
You don't need 1.18 to be safe from log4j
Eugenio Scalfi, yes I can confirm this bug began in Pre-Release 2 for 1.18. I have done testing with different versions, and I agree it does appear to be a problem with the switch to Java 17, additionally and especially since a way Error Code 0 can be produced is with an outdated Java version. I believe some people have had this problem on Windows too maybe, but I cannot confirm. I too am on Mac OS X El Capitan 10.11.6.
I sure do hope this issue is high on Mojang's priority list, regardless of whether they can do anything about it yet. Alienating a probably large-ish portion of their audience and community is something I know they would never choose to intentionally do. I hope this is fixed soon.
I am on Windows and am having this problem as well. Every time I attempt to log on to Minecraft, the game crashes and gives me an error code of 0. It's been 2 weeks now and I still have not been able to get on. Side note: I don't know if this is helpful, but I'll say it anyway. Back when the issue first started, in an attempt to fix it, I updated my windows to version 11, and then when I tried logging on, it worked. I then downloaded a shader mod a little while later, but after I did the problem immediately started again and I could not get past the loading screen. I have since removed the shader mod, and have tried reinstalling Minecraft and Java altogether multiple times, but nothing has worked. So I wonder if maybe this is a problem with Java itself and not Minecraft. Regardless, I really hope Microsoft is able to fix this problem soon, so I am able to play Minecraft again.
On Win 8.1 and the exact issue as well. It crashes at 100% world load.
I was just instructed by this place to go elsewhere as the issue is a technical issue and not a bug and they closed my report. They literally said "they don't have the manpower or time to work on technical issues" and closed my report MC-244766 as resolved, yeah, RESOLVED. This isn't mojang anymore this is Microsoft. I honestly believe they went the microsoft way of "releasing software that won't work on older windows machines and a required upgrade to Win 10 or 11 is the only way to go. That's just how Microsoft does things I guess. Not sure about you Mac guys but I don't believe this is any priority to them in the least.
1.17.1 still works. Not planning on buying a whole new system or paying for an upgrade from Win 8.1 just to play one game.
My son has a Macbook Air (11-inch Mid 2013). With OS X 10.10 (Yosemite) he had the problem with the 1.18 not loading.
We attempted to install the 17.0.1 version of OpenJDK (https://jdk.java.net/17/) then tried starting Minecraft using the MultiMC launcher, specifying this particular version. No luck.
To me it seemed clear that this particular version of Java was not happy with this version of OS X. We tried upgrading to 10.11 (El Capitan), and again, no luck.
Then upgraded again to 10.12 (Sierra), and lo and behold, it worked.
If your Mac is capable of going to 10.12, I would try upgrading to that. A good article with hardware requirements, and more importantly, direct links to older installers is here:
Can we please have an update on this bug/issue? If Microsoft is dropping support for Mac OS 10.11.6, it would be fair to let us know and to update the Minecraft system requirements to reflect this change. There is a great number of unresolved reports on this bug and thousands of unhappy campers in the online forums. It would be great if Mojang could confirm or correct our suspicions so we can move forward. To make things worse, those of us who play with our families on Realms can no longer access our 1.17 worlds because Realms doesn't allow older versions of the game. Perhaps this policy can be examined? Regardless, the Minecraft fans deserve to be updated. Thank you.
Ed Alaya, your problem seems to be different than the rest of ours; you can at least open Minecraft but cannot open any worlds, while we cannot open Minecraft full stop, the launcher preventing so. While your problem is also very severe, for all we know it may have a different cause. Still good to bring it here, but just wanted to point out to everyone that it may actually be an unrelated issue which also has to be fixed too. It's a shame your bug was marked as resolved, best of luck to you too that your issue will be fixed.
Same question as Scott Redinger a week ago; can we please get some info? This bug/issue is known for over a month now and there has yet to come an official reaction from Mojang. It does not have to be fixed soon, I can be patient, I just want to know if it is been worked on to get fixed or if not and Minecraft 1.18 is definitifely not playable on Mac OS 10.11.6.
I decided to try out what Darryl Lee wrote since I have the same computer (might be a 13-inch if that's important) ...and it worked!
I went from El Capitan 10.11 and upgraded to Sierra 10.12 and so far it's worth it since I can play on 1.18.1 now. I definitely recommend to try it if you're able to.
Edit: Thank you Darryl for the tip! I've had so many issues lately with the launcher and haven't been able to play for some months on and off now, so I'm genuinely thankful and relieved.
FYI, there is a separate bug report regarding Minecraft Java Edition and macOS 10.11: MC-242661.
I made a comment there recently that Java Edition 1.18+ games use Java 17, which is not compatible with macOS 10.11 (El Capitan) and below. It seems that those of us who are unable to upgrade to a newer operating system will not be able to play Caves & Cliffs: Part II, at least at the moment. I doubt that this bug will be fixed, but one can hope.
I suggest that those of you having this specific issue post your comments there.
In a duplicate report MC-242661, Mojang has confirmed the problem to be a compatibility issue with Java 17 and Mac OS 10.11 or older. The report was closed and marked as "resolved". They stated that we can still play older versions which is true however not on Realms. I would like to suggest that Mojang allow older versions on Realms.
This appeared in the launcher.
[media]So i guess Mojang has given up on this one. I'm sorry for those of you who cannot update macos.
Minecraft 1.18 crashes after clicking "PLAY" on launcher. I'm on Mac OS 10.11.6. "Error: Game crashed. An unexpected issue occurred and the game has crashed. We're sorry for the inconvenience. Exit Code: 0" Very disappointing start for the exciting new update ...and after waiting 4 weeks prior for the Launcher bug to be fixed.