Every time I launch Minecraft 1.13, it crashes.
I tried uninstalling Minecraft, completely deleting all prior files, and re-downloading Java edition. It continued crashing.
I also updated Java and re-installed my operating system. It continues to crash.
When it crashes, I get the following message:
(There's a longer error report than what I included below, but I'm limited as to what I can fit in this space).
"Minecraft launcher quit unexpectedly"
Process: launcher [307]Process: launcher [307]Path: /Applications/Minecraft.app/Contents/MacOS/launcherIdentifier: com.mojang.minecraftlauncherVersion: ??? (1)Code Type: X86-64 (Native)Parent Process: launchd [131]User ID: 501
Date/Time: 2018-07-25 18:39:52.321 -0700OS Version: Mac OS X 10.8.5 (12F45)Report Version: 10
Interval Since Last Report: 50827 secCrashes Since Last Report: 53Per-App Interval Since Last Report: 11 secPer-App Crashes Since Last Report: 7Anonymous UUID: 1601E4AC-624F-1FFE-4341-721DF2D5CD64
Crashed Thread: 0 CrBrowserMain Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000040
VM Regions Near 0x40:--> __TEXT 000000010d3fe000-000000010d455000 [ 348K] r-x/rwx SM=COW /Applications/Minecraft.app/Contents/MacOS/launcher
Thread 0 Crashed:: CrBrowserMain Dispatch queue: com.apple.main-thread0 libdispatch.dylib 0x00007fff89cedd17 _dispatch_barrier_async_f_slow + 501 org.chromium.ContentShell.framework 0x000000010ed706eb 0x10d79e000 + 228820272 org.chromium.ContentShell.framework 0x000000010e1772dc 0x10d79e000 + 103267483 org.chromium.ContentShell.framework 0x000000010e467580 0x10d79e000 + 134076164 org.chromium.ContentShell.framework 0x000000010e1777b3 0x10d79e000 + 103279875 org.chromium.ContentShell.framework 0x000000010e17b84a 0x10d79e000 + 103445226 org.chromium.ContentShell.framework 0x000000010eba434d 0x10d79e000 + 209969417 org.chromium.ContentShell.framework 0x000000010eb1bfd8 0x10d79e000 + 204390008 org.chromium.ContentShell.framework 0x000000010eb1c9ca 0x10d79e000 + 204415469 org.chromium.ContentShell.framework 0x000000010eb42f54 0x10d79e000 + 2059861210 org.chromium.ContentShell.framework 0x000000010eb42d34 0x10d79e000 + 2059806811 org.chromium.ContentShell.framework 0x000000010d7a0774 cef_initialize + 27612 0x000000010d5be19a CefInitialize(CefMainArgs const&, CefStructBase<CefSettingsTraits> const&, CefRefPtr<CefApp>, void*) + 15413 0x000000010d577eee RunLauncher + 180614 com.mojang.minecraftlauncher 0x000000010d4051dc main + 254015 libdyld.dylib 0x00007fff90a047e1 start + 1
Thread 1:: Dispatch queue: com.apple.libdispatch-manager0 libsystem_kernel.dylib 0x00007fff86868d16 kevent + 101 libdispatch.dylib 0x00007fff89cefdea _dispatch_mgr_invoke + 8832 libdispatch.dylib 0x00007fff89cef9ee _dispatch_mgr_thread + 54
Thread 2:0 libsystem_kernel.dylib 0x00007fff868686d6 __workq_kernreturn + 101 libsystem_c.dylib 0x00007fff8c6dcf1c _pthread_workq_return + 252 libsystem_c.dylib 0x00007fff8c6dcce3 _pthread_wqthread + 4123 libsystem_c.dylib 0x00007fff8c6c7191 start_wqthread + 13
Thread 3:0 libsystem_kernel.dylib 0x00007fff868686d6 __workq_kernreturn + 101 libsystem_c.dylib 0x00007fff8c6dcf1c _pthread_workq_return + 252 libsystem_c.dylib 0x00007fff8c6dcce3 _pthread_wqthread + 4123 libsystem_c.dylib 0x00007fff8c6c7191 start_wqthread + 13
Thread 4:0 libsystem_kernel.dylib 0x00007fff868686d6 __workq_kernreturn + 101 libsystem_c.dylib 0x00007fff8c6dcf1c _pthread_workq_return + 252 libsystem_c.dylib 0x00007fff8c6dcce3 _pthread_wqthread + 4123 libsystem_c.dylib 0x00007fff8c6c7191 start_wqthread + 13
Thread 5:: com.apple.NSURLConnectionLoader0 libsystem_kernel.dylib 0x00007fff86866686 mach_msg_trap + 101 libsystem_kernel.dylib 0x00007fff86865c42 mach_msg + 702 com.apple.CoreFoundation 0x00007fff907d5233 __CFRunLoopServiceMachPort + 1953 com.apple.CoreFoundation 0x00007fff907da916 __CFRunLoopRun + 10784 com.apple.CoreFoundation 0x00007fff907da0e2 CFRunLoopRunSpecific + 2905 com.apple.Foundation 0x00007fff8f225546 +[NSURLConnection(Loader) _resourceLoadLoop:] + 3566 com.apple.Foundation 0x00007fff8f283562 __NSThread__main__ + 13457 libsystem_c.dylib 0x00007fff8c6da772 _pthread_start + 3278 libsystem_c.dylib 0x00007fff8c6c71a1 thread_start + 13
Thread 6:0 libsystem_kernel.dylib 0x00007fff868686d6 __workq_kernreturn + 101 libsystem_c.dylib 0x00007fff8c6dcf1c _pthread_workq_return + 252 libsystem_c.dylib 0x00007fff8c6dcce3 _pthread_wqthread + 4123 libsystem_c.dylibLinked issues
is duplicated by 3
Attachments
Comments 7
Thanks for your reply. I do not use Discord.
I downloaded the Minecraft "legacy launcher" (I had to show it how to find Java 1.8, since it automatically looks for 1.6. This video does a good job of showing how to do that: https://www.youtube.com/watch?v=vB9dP4ALsqw&t=99s
The "legacy launcher" got a bit father than the most recent Java edition launcher. Minecraft attempted to load, and then I kept getting a message that "Java has quit unexpectedly."
I'm wondering if the issue is that my Macbook Air (which I bought in 2012) does not meet the requirements to run Minecraft 1.13?
Your computer is below the minimum system requirements: https://help.mojang.com/customer/en/portal/articles/325948-minecraft-java-edition-system-requirements
You need at least OS X 10.12 and Intel HD 4000.
But the legacy Launcher should still work.
Thanks a lot for your response.
Is there any reason, given my computer’s specs, that Java would continually crash when I try to launch Minecraft 1.13 using the legacy launcher?
Yes, 1.13 utilizes a new LWJGL which has higher requirements on the graphics drivers (uses parts which in 1.12 and below won't be used but now crash).
If you see any way to update your graphics drivers to versions higher 10.xx.xx.xx (current is 15.xx.xx.xx or 20.xx.xx.xx), then also 1.13 might run.
See the (Windows focused) ticket MC-32606
Of course you may ask the community support, linked below.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki
Are you using Discord? If yes, disable it and check if the issue persists.