Philipp Tögel
- p555t
- p555t
- Europe/Stockholm
- Yes
- No
MC-149225![[Mojang] Cory Scheviak](../../../data/avatars/users/92893.png){kind=small}
Macos 10.14.14
2019 Macbook Air 1,6 GHz Intel Core i5. Ram: 8 GB 2133 MHz LPDDR3, Intel UHD Graphics 617 1536 MB
Tried different Java runntimes - all the same effect.
Macos 10.14.14
2019 Macbook Air 1,6 GHz Intel Core i5. Ram: 8 GB 2133 MHz LPDDR3, Intel UHD Graphics 617 1536 MB (worked fine before 1.14)
Tried different Java runntimes - all the same effect.
Any info on how to fix this, though? Thx
The game crashes immediatelywhen clicking "play selected world" od double clicking on the world in the list.The game crashes immediately after selecting and starting
The game crashes immediately after selecting and starting a world on Mac OS Mojave, caused by libobjc.A.dylib
Macos 10.14.
142019 Macbook Air 1,6 GHz Intel Core i5. Ram: 8 GB 2133 MHz LPDDR3, Intel UHD Graphics 617 1536 MB (worked fine before 1.14)
Tried different Java runntimes - all the same effect.
Macos 10.14.4
2019 Macbook Air
1,6 GHz Intel Core i5.
Ram: 8 GB 2133 MHz LPDDR3,
Intel UHD Graphics 617 1536 MB
(worked fine before 1.14)
Tried different Java runntimes - all the same effect.
The game starts up fine. when entering a World (local or connecting to a server), the game immediately crashes after the command to enter the world (doesen't matter where i click). After this, both, a minecraft crash report, and a OS-report come up. Both are attatched to this ticket.
update: I tried downgrading the MC versions: 1.13.2 produced the same error, 1.13.1 was playable.
# # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x00007fff7abeee02, pid=22587, tid=775 # # JRE version: Java(TM) SE Runtime Environment (8.0_74-b02) (build 1.8.0_74-b02) # Java VM: Java HotSpot(TM) 64-Bit Server VM (25.74-b02 mixed mode bsd-amd64 compressed oops) # Problematic frame: # C [libobjc.A.dylib+0x7e02] lookUpImpOrForward+0x5b # # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again # # If you would like to submit a bug report, please visit: # http://bugreport.java.com/bugreport/crash.jsp # The crash happened outside the Java Virtual Machine in native code. # See problematic frame for where to report the bug. #
please come vote for ticket nr 149225 which is the active duplicate for this one!
WE NEED YOUR VOTES!
please come vote for ticket nr 149225 which is the active duplicate for this one!
WE NEED YOUR VOTES!
![[Helper] Johnibur](../../../data/avatars/users/28381.png){kind=small}
Of course Philipp Tögel. 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.
Did this occur only after the update to 1.14 for you as well? Everything fine before that?
@Johnibur This crash only affects Mac OS (libobjc.A.dylib).
The crash seems to happen in a MacOS System library, that's true. But it only occurs with Minecraft and only after the update to 1.14 - so i figured it kinda belongs here anyways.
Would be a bright shame if i couldn't play MC anymore because of an update
. PLZ Help!
Thanks for your kind reply, @Johnibur
i updated the title - let's hope for a fix!
@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.
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!
@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?)
Big thanks to the Mods and the People at Mojang! Single player worlds now work on the OPs MacBookAir. Multiplayer not yet tested...