The game crashes immediately after selecting and starting a world on Mac OS Mojave, caused by libobjc.A.dylib

Of course @unknown. I just wanted to pinpoint the cause to show relevance. In fact, you should update your title summary because by reading it, it may lead people to think that the problem is on your side (game doesn't usually crash that way on other platforms): make your title clearer, appending something like "on Mac OS, caused by libobjc.A.dylib". It will add more visibility to this ticket.
Also rest assure that crashes are always addressed in time, whatever the platform is as long as it is a supported one.

Thanks for your kind reply, @Johnibur

i updated the title - let's hope for a fix!

I am also experiencing this issue in MacOS 10.13.6. It occurs with the embedded JVM, and also the latest JVM from Oracle. For me I'm trying to create a world when it crashes. Haven't tried to connect to a server yet.

Try updating java, maybe that'll fix it

@Josh74000MC "Try updating java, maybe that'll fix it"

Well i have done that of course, as i stated in the description: I tried many different JVM Versions, none of them worked.

It must be a mac issue then, it doesn't affect windows 10 as I've not had an issue with crashes upon loading world, gonna try to see if I can reproduce this on windows 10 and if it does crash, it possibly affects windows, if no crash happens, then windows isn't affected.

@unknown No need to, this is caused by a Mac Objective-C library.

When could we expect this to be fixed? I feel like this should be a high priority issue, as it is fundamentally game breaking for many people

YES, IT SHOULD BE. Extremely triggering. 

I even have the same issues on my macbook.

My sister's windows laptop also crashes and refuses to play the new update and that's a windows with the issues for crashing. It stopped working even with downgrading.

At this stage if I want to play minecraft, I'm forced to play on 1.13.2

I hope they solve this issue quickly really.

i would have expected issues with my mac since i'm running on a late 2012 model, but i'm surprised that it's a general mac issue _{(and also somewhat glad because i probably wont have to get a new computer just for minecraft if this gets fixed)}

it crashes for me when i try to load or create a singleplayer or multiplayer world, and when i select my friend's realm (not load, just select), with exactly the same crash report. i can run 1.13.2 _{(with vbos enabled in case you were wondering)} just fine.

having the exact same issue with 1.14, in 1.13 works perfect

How would I contact the CEO directly about this? 

Would be great with some response from the devs?

Just sending us back to 1.13.2 won't really fix the problem when we want to play the new update?🙂 

Exactly. If anybody finds a way to contact them directly, let me know. 1.14 awaits. 

i feel like this (the bug tracker) is already the best way to contact mojang about this. if we want this to get patched we might just need more votes

side note: my brother who has the same mac on high sierra (im on mojave) can run 1.14 just fine

Plus one with the same problem.
2015 Macbook Air, MacOS Sierra 10.12.6

Everything is works fine except MC 1.14
No one version 1.14 like pre-release, doesn`t work at all.
1.13.2 and lower still perfectly work.

I am on High Sierra 10.13.6. I'm experiencing the same problem, both with the embedded Java version and using the latest oracle version of Java and forcing the launcher to use it.

Thx everyone for speaking up if you also experience this crash!

In case you have not done this already, here's a friendly reminder:

Don't forget to vote for this ticket!

As we need some attention from the devs...

thx! 😉

I already voted.   I cannot play 1.14 at all on my MacBook Pro running Sierra.   When creating a new world, or when opening an existing one, I get the "libobjc" error that everyone else is seeing.

I have also tried the latest Oracle Java, and also the built-in, and both crash the same way.

Mojang please help!  

ho do I vote for the issue?

I just want to say (not as a Moderator) that 1.14 is working on my 2016 MacBook Pro running Mojave

Diego, there's a vote button to the right of the issue description

About how many votes will it take to get noticed? 

So just read 1.14.1 Pre-Release 1 has been released, and we can't even play 1.14.

Hellooooo, Mojang? This has been a problem before 1.14 aswell. Who can fix this? 

@Rolf Olav Riddervold, are you saying that this is still happening to you in the pre-release?

Also, is anyone not running Mojave 10.14.4 specifically (I am not). This might be a macOS bug.

Yes, I just tried it in 1.14.1 Pre-Release and it's still crashing

And are you running 10.14.4? (You can see this by clicking  > About this Mac)

Yeah Mojave 10.14.4

@unknown And what kind of Mac do you have? I believe this issue is a macOS bug since I'm not experiencing it on 10.14.5. I want to confirm that it's not a hardware variant issue.

@ezfe How can you be on 1.14.5 ?? My Macbook Air is on 1.14.4 and it says it's up do date... (Wikipedia also states 1.14.4 is the most recent version of MacOs).

Also: It is a MacOs bug, but one that only occurs with minecraft, and only after the update to 1.14 - that's why we put our hopes in Mojang :/

Also: Why does everyone post that MC is running on some of their Machines? I have a Macbook here, that can run 1.14, but it needs to run on my friends Computer, too, see? (He bought the game, just as i did 😉, i guess it's fair that he want's to play it, then. Just because it runs on my Mac doesn't solve the problem for him, right?)

I am running a pre-release. They're available from Apple if you sign up.

I'm not closing this because I'm not confident enough yet to say that this isn't a machine-specific issue rather than a macOS issue.

I think I posted a picture of my specs now? 

Version: 10.14.4

MacBook Pro (Retina, 13-inch, Early 2015)

Processor: 2,7 GHz Intel Core i5

Memory: 8GB 1867 MHz DDR3

Graphics: Intel Iris Graphics 6100 1536

@Philipp Tögel, this is NOT just after 1.14. It happened to me in the latest patch (not pre-release) before 1.14. I would sometimes get a crash, sometimes it would work. But not like this as it's not playable at all now.

Compared to my friends Mac, I thought the game run quite slow, with loads of FPS drops. My friend plays on a MacBook Air with not as good specs as mine.

I just checked his Mac-version and he is in fact on version 10.14.2, and he can play minecraft flawlessly without any FPS drops. My guess now is that this is a Mac problem? 

@Ezekiel (ezfe) So you can play on pre-release of a mac? Where do I sign up🙂 

@[ [Mod] Ezekiel (ezfe)|https://bugs.mojang.com/secure/ViewProfile.jspa?name=ezekielelin],
Is there any way to get it or to have this problem fixed without having to pay to be a Mac developer?
The only thing you can download for free there is Xcode

You can download the beta version of macOS from the public beta program:

beta.apple.com

You should be sure to backup your computer before installing pre-release software.

10.14.5 will likely be publicly released in the next two weeks. I'm not responsible for any loss of data due to installing pre-release software!

Were you able replicate the issue? For example on a different OS version?

@unknown No, which is why I indicated above that I'm not sure this is the reason. If someone does install 10.14.5 and the problem goes away, then I will close this ticket. However since I cannot test that I won't close it.

I'm reporting this crash not happening on a *Mojave 10.14.4* but running old Java *1.8.0_74*.

I updated to Mojave 10.14.5 and still experience the same error.

Here is my dynamic library file

-rwxr-xr-x  1 root  wheel  28112240  4 May 15:29 libobjc.A.dylib

I also note:

lrwxr-xr-x    1 root  wheel        15  8 May 16:09 libobjc.dylib -> libobjc.A.dylib

Feynman:lib $ md5 libobjc.A.dy*

MD5 (libobjc.A.dylib) = e31ab7a956e2fe8a98ed6cfc64da5a23

johnibur, i think you might be confused. mojave is a version of mac os (10.14.x) and not its own program. you can check out what mac os you're using by clicking the apple icon in the top left and then selecting "about this mac"

i'll also note im running 10.14.1 rather than 10.14.4

@Johnibur 

I now uninstalled the latest version of Java and reinstalled your version of Java ***1.8.0_74* and I am still crashing. It did not work. 

Further details:

The crash does not appear in 19w09a but appears in the next build 19w11a

From my quick reading, I'm thinking that something is being deallocated twice, or deallocated before it was allocated. Even if I just open minecraft in a buggy version and close it, the game crashes.

I'm not using Mac myself. I'm just reporting for a friend who is playing Minecraft 1.14 on MacOS Mojave 10.14.4 with Java 1.8.0_74 without this JVM crash. Here is a F3 screenshot:

So seems like 10.14.5 is not a solution - This ticket will certainly stay open

@unknown, Could you reproduce the crash and then file a report with the Feedback Application under 10.14.5? It will gather a system diagnose for you.

I can re-create the same as David above - 19w09a works, 19w11a crashes on creating a new world, or opening an existing world.

 MacBook Pro (Retina, 15-inch, Late 2013)

Running Sierra - 10.12.6

i also tried 19w09a & 19w11a and i got the same results; 09a worked, 11a didn't. i'm running a mac mini (late 2012) with osx mojave 10.14.1 for reference

(my brother has the same mac with osx high sierra 10.13.3 and can run 1.14 fine)

I’m having the same exact issue

iMac late 2009
Mac OS X 10.12.6

I've had this issue since the first snapshot of 1.14 from 1 through 5 then the full release and prereleases 1 & 2. please fix soon

@unknown, would love to get an update soon on what's going on? 

1.14 was released on 23. april and people confirm that this has been a problem on earlier snapshots before it was even released. It's 13. may!! The newest release of the game is not playable at all. 23 people has voted for this and there are over 50 comments here now. 

Please, we would like to play 1.14.

Hi @unknown,

I understand that this is annoying-I’ve been in the same situation and I wanted to see the game fixed. I’ll continue to surface this issue internally, both with Mojang and Apple.

Thanks for your patience!

I'm getting the same issues. Windows 8.1 Intel Core i3-4005U CPU @ 1.70 GHz

@unknown, your issue is MC-32606, not the one described in this ticket.

I just uploaded hs_err_pid627.log
my mac specs are
MacBook Pro (13-inch, Mid 2012) (just realised how old my computer is, still works fine)
2.9 GHz Intel Core i7
8 GB 1600 MHz DDR3
intel HD Graphics 4000 1536 MB

i have attached hs_err_pid610.log, i run a mac mini (late 2012) with a 2.5 ghz intel core i5, 8 gb 1600 mhz ddr3, and intel hd graphics 4000 w 1536 mb.

my brother also runs the same mac mini with the same intel core and graphics, but runs 10.13.3 and has 16 gb 1600 mhz ddr3, and he can run 1.14.0 (haven't tried 1.14.1)

MacBook Air (13-inch, Early 2014) 

Running: 10.13.6

Processor: 1.4 GHz Intel Core i5

Memory: 4 GB 1600 MHz DDR3

Graphics: Intel HD Graphics 5000 1536 MB

Here's my crash report: https://pastebin.com/TFuCeiMq

MacBook Air
MacBookAir7,2
Intel Core i5, 1.6 GHz
4 GB

Can anybody on this report please attach the launcher logs leading up to this crash? Not the crash report, the logs. It would be very beneficial to see this.

Cory, I uploaded a text file of the crash, I believe it is the launcher logs you are after.
"Terminal saved output - MC Crash"

i have added crash report hs_err_pid2184.log, and the game output (i believe this is the log you are refering to, if not please specify how to access it) as a text file (sSolstaCrashText.rtf) and as an image (Screen Shot 2019-05-16 at 7.44.09 pm.png). these all refer to the same crash attempting to create a singleplayer world. i find it strange that the log doesnt output anything between the startup of the menu screen and the crash itself

i discovered that i had turned off the debug text. i was unable to copy all of the log to a text file, but i was able to get another screenshot, and there is still absolutely no log between the loading of the menu and the crash. i would do a screen recording but my computer cant seem to handle obs and minecraft at the same time