You don't need 1.18 to be safe from log4j
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
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?
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).
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
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.
This appeared in the launcher.
So i guess Mojang has given up on this one. I'm sorry for those of you who cannot update macos.