So I've had this problem ever since the snapshots for Update Aquatic have come out. When it first crashed on me I thought it was a simple matter of the update itself. So I waited for a week. I got the same result. I continued believing it was the snapshots, but people started talking about all the wonders of this update. I researched a few of the bugs people were having to attempt to solve my own dilemma. One of these was that Java was outdated, so I updated Java, but I got the same result. I heard there was a custom resolution bug, so I checked it, but my game was already set to standard.
So, I'm in a strange situation. My computer handles 1.12.2 surprisingly well for an old MacBook, so theoretically 1.13 shouldn't be a "your computer is too old" kind of problem. I've listed all the information I could squeeze out of my computer. If anyone can help me out it would be a Godsend.
Process: java [616]
Path: /Applications/Minecraft.app/Contents/runtime/jre-x64/1.8.0_74/bin/java
Identifier: java
Version: 1.0 (1.0)
Code Type: X86-64 (Native)
Parent Process: launcher [608]
Responsible: launcher [608]
User ID: 501
Date/Time: 2018-02-24 20:44:53.367 -0600
OS Version: Mac OS X 10.10.5 (14F2511)
Report Version: 11
Anonymous UUID: D0D822A6-488E-4199-EAB6-BB0C184D80A6
Time Awake Since Boot: 2600 seconds
Crashed Thread: 0 Java: Client thread Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGABRT)
Exception Codes: KERN_INVALID_ADDRESS at 0x00000000000015e0
VM Regions Near 0x15e0:
-->
__TEXT 00000001051ee000-0000000105200000 [ 72K] r-x/rwx SM=COW /Applications/Minecraft.app/Contents/runtime/jre-x64/1.8.0_74/bin/java
Application Specific Information:
abort() called
Thread 0 Crashed:: Java: Client thread Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x00007fff875eb286 __pthread_kill + 10
1 libsystem_c.dylib 0x00007fff860f19a3 abort + 129
2 libjvm.dylib 0x000000010576f68b os::abort(bool) + 25
3 libjvm.dylib 0x000000010589354e VMError::report_and_die() + 2304
4 libjvm.dylib 0x00000001054d29b3 report_vm_error(char const*, int, char const*, char const*) + 84
5 libjvm.dylib 0x00000001054d47df MachODecoder::decode(unsigned char*, char*, int, int*, char const*) + 21
6 libjvm.dylib 0x00000001054d4404 Decoder::decode(unsigned char*, char*, int, int*, char const*) + 162
7 libjvm.dylib 0x000000010576f226 os::dll_address_to_function_name(unsigned char*, char*, int, int*) + 262
8 libjvm.dylib 0x0000000105534a29 frame::print_C_frame(outputStream*, char*, int, unsigned char*) + 221
9 libjvm.dylib 0x00000001054d2580 print_native_stack(outputStream*, frame, Thread*, char*, int) + 111
10 libjvm.dylib 0x000000010589254b VMError::report(outputStream*) + 2553
11 libjvm.dylib 0x0000000105893046 VMError::report_and_die() + 1016
12 libjvm.dylib 0x00000001054d29b3 report_vm_error(char const*, int, char const*, char const*) + 84
13 libjvm.dylib 0x00000001054d47df MachODecoder::decode(unsigned char*, char*, int, int*, char const*) + 21
14 libjvm.dylib 0x00000001054d4404 Decoder::decode(unsigned char*, char*, int, int*, char const*) + 162
15 libjvm.dylib 0x000000010576f226 os::dll_address_to_function_name(unsigned char*, char*, int, int*) + 262
16 libjvm.dylib 0x0000000105534a29 frame::print_C_frame(outputStream*, char*, int, unsigned char*) + 221
17 libjvm.dylib 0x0000000105892173 VMError::report(outputStream*) + 1569
18 libjvm.dylib 0x0000000105893046 VMError::report_and_die() + 1016
19 libjvm.dylib 0x00000001054d29b3 report_vm_error(char const*, int, char const*, char const*) + 84
20 libjvm.dylib 0x00000001054d47df MachODecoder::decode(unsigned char*, char*, int, int*, char const*) + 21
21 libjvm.dylib 0x00000001054d4404 Decoder::decode(unsigned char*, char*, int, int*, char const*) + 162
22 libjvm.dylib 0x000000010576f226 os::dll_address_to_function_name(unsigned char*, char*, int, int*) + 262
23 libjvm.dylib 0x0000000105534a29 frame::print_C_frame(outputStream*, char*, int, unsigned char*) + 221
24 libjvm.dylib 0x0000000105892173 VMError::report(outputStream*) + 1569
25 libjvm.dylib 0x0000000105892ef9 VMError::report_and_die() + 683
26 libjvm.dylib 0x00000001057712b6 JVM_handle_bsd_signal + 1131
27 libjvm.dylib 0x000000010576d51b signalHandler(int, __siginfo*, void*) + 47
28 libsystem_platform.dylib 0x00007fff8b964f1a _sigtramp + 26
29 liblwjgl_opengl.dylib 0x00000001225f67fe 0x1225e9000 + 55294
30 ??? 0x00000001068074a0 0 + 4404049056
31 ??? 0x0000000106807710 0 + 4404049680
32 ??? 0x0000000106807710 0 + 4404049680
33 ??? 0x0000000106807710 0 + 4404049680
34 ??? 0x00000001068077e4 0 + 4404049892
35 ??? 0x000000010680798d 0 + 4404050317
36 ??? 0x0000000106807710 0 + 4404049680
37 ??? 0x000000010680798d 0 + 4404050317
38 ??? 0x00000001068004e7 0 + 4404020455
39 libjvm.dylib 0x00000001055d739e JavaCalls::call_helper(JavaValue*, methodHandle*, JavaCallArguments*, Thread*) + 1710
40 libjvm.dylib 0x000000010560e110 jni_invoke_static(JNIEnv_*, JavaValue*, _jobject*, JNICallType, _jmethodID*, JNI_ArgumentPusher*, Thread*) + 447
41 libjvm.dylib 0x0000000105606e8a jni_CallStaticVoidMethod + 349
42 java 0x00000001051f193e JavaMain + 2481
43 java 0x00000001051f359c -[JavaLaunchHelper launchJava:] + 42
44 com.apple.Foundation 0x00007fff90032da0 __NSThreadPerformPerform + 293
45 com.apple.CoreFoundation 0x00007fff8e65a821 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
46 com.apple.CoreFoundation 0x00007fff8e64c9ad __CFRunLoopDoSources0 + 269
47 com.apple.CoreFoundation 0x00007fff8e64bfdf __CFRunLoopRun + 927
48 com.apple.CoreFoundation 0x00007fff8e64b9f8 CFRunLoopRunSpecific + 296
49 java 0x00000001051f4463 CreateExecutionEnvironment + 871
50 java 0x00000001051f01ac JLI_Launch + 1952
51 java 0x00000001051f64c0 main + 101
52 java 0x00000001051efa04 start + 52
Thread 1:
0 libsystem_kernel.dylib 0x00007fff875eb136 __psynch_cvwait + 10
1 com.apple.Foundation 0x00007fff8ffdefa8 -[NSCondition wait] + 237
2 com.apple.Foundation 0x00007fff8ffcfe3e -[NSObject(NSThreadPerformAdditions) performSelector:onThread:withObject:waitUntilDone:modes:] + 823
3 com.apple.Foundation 0x00007fff8ffcfa89 -[NSObject(NSThreadPerformAdditions) performSelectorOnMainThread:withObject:waitUntilDone:] + 131
4 java 0x00000001051f37b5 JVMInit + 251
5 java 0x00000001051f0cf1 JLI_Launch + 4837
6 java 0x00000001051f64c0 main + 101
7 java 0x00000001051f40f5 apple_main + 92
8 libsystem_pthread.dylib 0x00007fff8d51505a _pthread_body + 131
9 libsystem_pthread.dylib 0x00007fff8d514fd7 _pthread_start + 176
10 libsystem_pthread.dylib 0x00007fff8d5123ed thread_start + 13
Thread 2:: Dispatch queue: com.apple.libdispatch-manager
0 libsystem_kernel.dylib 0x00007fff875ec232 kevent64 + 10
1 libdispatch.dylib 0x00007fff8d1ca26e _dispatch_mgr_thread + 52
Thread 3:
0 libsystem_kernel.dylib 0x00007fff875eb136 __psynch_cvwait + 10
1 libjvm.dylib 0x000000010576bc76 os::PlatformEvent::park() + 192
2 libjvm.dylib 0x0000000105748e32 ParkCommon(ParkEvent*, long) + 42
3 libjvm.dylib 0x0000000105749708 Monitor::IWait(Thread*, long) + 168
4 libjvm.dylib 0x0000000105749971 Monitor::wait(bool, long, bool) + 375
5 libjvm.dylib 0x00000001058aa965 GangWorker::loop() + 179
6 libjvm.dylib 0x000000010576feda java_start(Thread*) + 246
7 libsystem_pthread.dylib 0x00007fff8d51505a _pthread_body + 131
8 libsystem_pthread.dylib 0x00007fff8d514fd7 _pthread_start + 176
9 libsystem_pthread.dylib 0x00007fff8d5123ed thread_start + 13
...
Related issues
Attachments
Comments

My computer handles 1.12.2 surprisingly well for an old MacBook, so theoretically 1.13 shouldn't be a "your computer is too old" kind of problem.
As of Minecraft 1.13, Minecraft uses JLWGL 3 instead of JLWGL 2. I know that Linux 32 bit systems are not supported by JLWGL 3 and therefore you can't play Minecraft with those systems anymore. Maybe the same applies to old macOS systems as well, I don't know.
Either way, this is a technical support issue; this site is for bug reports only. We do not have the resources to provide you with technical support.
Please contact the community support, linked below.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki

Makes sense. I thought (and hoping) it was just a bug. Thanks for looking at it.

Something similar happened to me but that was 1.13 fully released and it still does it