Hi. I'm relatively new to Mac OS X and Minecraft. I've been playing Minecraft for a year+ on an old Macbook Air (Mavericks) with no problem. I just got a new Macbook Pro with El Capitan (10.11) and discovered it won't run anything beyond 1.7.10. If I try 1.8 or higher, it builds the world, drops me in, I might hear a pig snort, and then it crashes. Any version from 1.7.10 seems to work just fine. (I didn't try every one). With the new MBP, I downloaded a new copy of the Minecraft Launcher (version 1.6.61). I feel like I'm doing some simple thing wrong, but I can't figure it out.
[14:38:01] [Client thread/INFO]: Setting user: CreeperGirlMC [14:38:01] [Client thread/INFO]: (Session ID is token:40d510b53b11456f8400065d5e0a9430:42c0a1858b934ab799fee25078fd132d) [14:38:02] [Client thread/INFO]: LWJGL Version: 2.9. [14:38:02] [Client thread/INFO]: Reloading ResourceManager: Default [14:38:02] [Sound Library Loader/INFO]: Starting up SoundSystem... [14:38:03] [Thread-6/INFO]: Initializing LWJGL OpenAL [14:38:03] [Thread-6/INFO]: (The LWJGL binding of OpenAL. For more information, see http://www.lwjgl.org) [14:38:03] [Thread-6/INFO]: OpenAL initialized. [14:38:03] [Sound Library Loader/INFO]: Sound engine started [14:38:04] [Client thread/INFO]: Created: 512x512 textures-atlas [14:38:11] [Server thread/INFO]: Starting integrated minecraft server version 1.8 [14:38:11] [Server thread/INFO]: Generating keypair [14:38:12] [Server thread/INFO]: Preparing start region for level 0 [14:38:12] [Server thread/INFO]: Changing view distance to 12, from 10 [14:38:13] [Server thread/INFO]: CreeperGirlMC[local:E:2b218d9f] logged in with entity id 225 at (27.104584470027113, 83.40468679073513, -362.06973686140157) [14:38:13] [Server thread/INFO]: CreeperGirlMC joined the game [14:38:17] [Server thread/WARN]: Can't keep up! Did the system time change, or is the server overloaded? Running 2907ms behind, skipping 58 tick(s)
Here's the output from the 'Game Output' window:
Java HotSpot(TM) 64-Bit Server VM warning: Using incremental CMS is deprecated and will likely be removed in a future release Completely ignored arguments: [--nativeLauncherVersion, 302] [14:51:29] [Client thread/INFO]: Setting user: CreeperGirlMC [14:51:29] [Client thread/INFO]: (Session ID is <censored>) [14:51:30] [Client thread/INFO]: LWJGL Version: 2.9.2 [14:51:31] [Client thread/INFO]: Reloading ResourceManager: Default [14:51:31] [Sound Library Loader/INFO]: Starting up SoundSystem... [14:51:31] [Thread-6/INFO]: Initializing LWJGL OpenAL [14:51:31] [Thread-6/INFO]: (The LWJGL binding of OpenAL. For more information, see http://www.lwjgl.org) 2016-04-05 14:51:31.429 java[1467:73460] 14:51:31.428 WARNING: 140: This application, or a library it uses, is using the deprecated Carbon Component Manager for hosting Audio Units. Support for this will be removed in a future release. Also, this makes the host incompatible with version 3 audio units. Please transition to the API's in AudioComponent.h. [14:51:31] [Thread-6/INFO]: OpenAL initialized. [14:51:31] [Sound Library Loader/INFO]: Sound engine started [14:51:32] [Client thread/INFO]: Created: 512x512 textures-atlas [14:51:37] [Server thread/INFO]: Starting integrated minecraft server version 1.8 [14:51:37] [Server thread/INFO]: Generating keypair [14:51:38] [Server thread/INFO]: Preparing start region for level 0 [14:51:38] [Server thread/INFO]: Changing view distance to 12, from 10 [14:51:39] [Server thread/INFO]: CreeperGirlMC[local:E:d1fb6261] logged in with entity id 225 at (27.104584470027113, 83.40468679073513, -362.06973686140157) [14:51:39] [Server thread/INFO]: CreeperGirlMC joined the game [14:51:43] [Server thread/WARN]: Can't keep up! Did the system time change, or is the server overloaded? Running 2920ms behind, skipping 58 tick(s)
That's why I'm reaching out here. I can't find anything that I'm obviously doing wrong nor can I find anything in a log anywhere that tells me something has gone wrong. Can you point me where I might look or is there something I might have missed somewhere? Is there another log that is more informative? Is there some installation step I'm overlooking that's required for El Capitan? Where am I going wrong?
I'm not a Mac user so I don't really know about Mac specific issues.
Usually a Java exception is created and logged which points at a specific cause.
The three biggest issues that create version specific failures are (1) minecraft save data incompatibilities between versions [this generally doesn't cause a crash] (2) minecraft option / settings incompatibilities between versions [ this generally causes a Java exception of some kind] (3) changes in the way minecraft uses the Open GL APIs hitting bugs in the video driver that were always there waiting to be encountered. [ this generally causes a Java exception]
Other problems usually affect all versions of minecraft equally.
If the minecraft window just goes *poof* and disappears then the JVM is terminating in an abnormal fashion... are there any Mac specific places you can look for process failures? an event log, /var/log/messages or whatever?
Hey gerbil. I did some snooping and found a system console that I cleared out and then watched as I ran Minecraft using version 1.8 that causes the crash (and the crash goes like this: minecraft launches, the world begins to build, I am dropped into the world, I begin to hear music, then it freezes, after a few seconds...maybe 10 or less, it crashes back to the Launcher).
Buried in this log report I found an entry: 'DumpGPURestart'
Tue Apr 5 19:34:20 2016
Event: GPU Reset
Date/Time: Tue Apr 5 19:34:20 2016
Application: java
Path:
OS Version: Mac OS X Version 10.11.4 (Build 15E65)
Graphics Hardware: Intel Iris Pro
Signature: 8013
Report Data:
===========================================================================
Intel GPU Hang Summary
version 1.0.0
===========================================================================
-- Summary of Status for ALL Rings --
MAIN Ring is hung in a batch buffer <-- ROOT CAUSE!
MEDIA Ring is idle
BLT Ring is waiting on a semaphore
VEBOX Ring is idle
===========================================================================
Essential Ring Registers
===========================================================================
-- MAIN Ring --
RING_HEAD = 0x012688a0 (offset = 0x000688a0, wrap count = 9, wait_for_cond = 0x0)
RING_TAIL = 0x0006e890 (offset = 0x0006e890)
RING_START = 0x10205000 (offset = 0x10205000)
RING_CTRL = 0x000ff001 (enabled, auto report disabled (0x00), not waiting, semaphore not waiting, length = 0x100 4KB pages)
-- MEDIA Ring --
RING_HEAD = 0x000000f0 (offset = 0x000000f0, wrap count = 0, wait_for_cond = 0x0)
RING_TAIL = 0x000000f0 (offset = 0x000000f0)
RING_START = 0x10325000 (offset = 0x10325000)
RING_CTRL = 0x0000f001 (enabled, auto report disabled (0x00), not waiting, semaphore not waiting, length = 0x010 4KB pages)
-- BLT Ring --
RING_HEAD = 0x28e03178 (offset = 0x00003178, wrap count = 327, wait_for_cond = 0x0)
RING_TAIL = 0x000050d0 (offset = 0x000050d0)
RING_START = 0x10305000 (offset = 0x10305000)
RING_CTRL = 0x0001f401 (enabled, auto report disabled (0x00), not waiting, semaphore is waiting, length = 0x020 4KB pages)
-- VEBOX Ring --
RING_HEAD = 0x00000078 (offset = 0x00000078, wrap count = 0, wait_for_cond = 0x0)
RING_TAIL = 0x00000078 (offset = 0x00000078)
RING_START = 0x10335000 (offset = 0x10335000)
RING_CTRL = 0x0000f001 (enabled, auto report disabled (0x00), not waiting, semaphore not waiting, length = 0x010 4KB pages)
- One or more rings were waiting on a semaphore
RVSYNC = 0x00000000
RVESYNC = 0x00000000
RBSYNC = 0x00033204
BRSYNC = 0x0009538a
BVSYNC = 0x00000000
BVESYNC = 0x00000000
VBSYNC = 0x00033204
VRSYNC = 0x0009538a
VVESYNC = 0x00000000
- Other registers associated with guilty ring -
BB_ADDR = 0x158752a9 (offset = 0x158752a8, valid = 0x1)
BB_STATE = 0x00000000
IPEIR = 0x00000000
ACTHD = 0x158752a8
EIR = 0x00000000
EMR = 0xffffffff
ESR = 0x00000000
INSTPM = 0x00006080
INSTPS = 0x80000208
UHPTR = 0x00000000
- Common Slice INST_DONE register -
Some Common Slice engines are NOT DONE.
- INSTDONE_CS (=0xfffffe97): Not done = HiZ, IZ, SBE, RCZ,
===========================================================================
Details for Hung/Stuck ring: MAIN
===========================================================================
Last instruction header executed: 0x7b000005 (IPEHR=0x7b000005)
-> Use AubList to decode: Aublist -d 0x7b000005
Some Main engines are NOT DONE.
INSTDONE = 0xffdf7c19: Not done = VF, VS, DS, GS, SOL, CL, SF, GAFS,
- PAGETABLE_RCS_PP_DIR_BASE = 0x173f0000
- PAGETABLE_PP_PFIR = 0x00000000
- PAGETABLE_PP_PFD = 0x00000000
- PAGETABLE_BCS_PP_DIR_BASE = 0x173f0000
- PAGETABLE_BCS_PP_DCLV = 0xffffffff
- PAGETABLE_BCS_SWCTRL = 0x00000002
- PAGETABLE_VCS_PP_DIR_BASE = 0x10000000
- PAGETABLE_VCS_PP_DCLV = 0xffffffff
- PAGETABLE_VECS_PP_DIR_BASE = 0x10000000
- PAGETABLE_VECS_PP_DCLV = 0xffffffff
-----------------------------------
Dumping MAIN ring buffer contents:
Start Offset: 0x00068710
Head Offset : 0x0006889c (Adjusted to previous instruction)
End Offset : 0x000688c8
-----------------------------------
Offset Value
------------------------
0x00068710 : 0x10400003
0x00068714 : 0x00000000
...
...
...
It goes on for pages. Looks like address : value pairs, registers and their values, and hex dumps (I think).
Further along, I came across 'java crash report': (this I include in its entirety--it's long)
Process: java [781]
Path: /Applications/Minecraft.app/Contents/runtime/jre-x64/1.8.0_74/bin/java
Identifier: net.java.openjdk.cmd
Version: 1.0 (1.0)
Code Type: X86-64 (Native)
Parent Process: launcher [750]
Responsible: java [781]
User ID: 501
Date/Time: 2016-04-05 19:34:26.597 -0400
OS Version: Mac OS X 10.11.4 (15E65)
Report Version: 11
Anonymous UUID: 2E37DC47-4956-1C00-FE77-3D62E19AD0DD
Sleep/Wake UUID: FCEE34F5-9E1B-4AAD-9A2B-DB95275B098F
Time Awake Since Boot: 2700 seconds
Time Since Wake: 2100 seconds
System Integrity Protection: enabled
Crashed Thread: 3 Java: Client thread
Exception Type: EXC_BAD_ACCESS (SIGABRT)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000109560000
Exception Note: EXC_CORPSE_NOTIFY
VM Regions Near 0x109560000:
__LINKEDIT 0000000109552000-0000000109560000 [ 56K] r--/rwx SM=COW /Applications/Minecraft.app/Contents/runtime/jre-x64/1.8.0_74/lib/libjava.dylib
--> VM_ALLOCATE 0000000109560000-0000000109561000 [ 4K] r--/rwx SM=PRV
shared memory 0000000109561000-0000000109562000 [ 4K] r--/rw- SM=SHM
Application Specific Information:
abort() called
Application Specific Signatures:
Graphics hardware encountered an error and was reset: 0x00008013
VIRTUAL REGION
REGION TYPE SIZE COUNT (non-coalesced)
=========== ======= =======
Accelerate.framework 128K 2
Activity Tracing 2048K 2
CG backing stores 7772K 5
CG image 1056K 5
CG shared images 272K 8
CoreAnimation 20K 4
CoreUI image data 1008K 8
CoreUI image file 384K 6
Dispatch continuations 16.0M 2
Kernel Alloc Once 8K 3
MALLOC 321.9M 78
MALLOC guard page 32K 7
MALLOC_LARGE (reserved) 4096K 4 reserved VM address space (unallocated)
Memory Tag 242 12K 2
Memory Tag 249 156K 3
OpenCL 8K 2
OpenGL GLSL 256K 4
Process Corpse Info 2048K 2
STACK GUARD 56.2M 45
Stack 47.2M 45
Stack Guard 312K 27
VM_ALLOCATE 2.3G 136
VM_ALLOCATE (reserved) 119.5M 3 reserved VM address space (unallocated)
__DATA 20.8M 263
__GLSLBUILTINS 2588K 2
__IMAGE 528K 2
__LINKEDIT 101.9M 30
__TEXT 164.3M 264
__UNICODE 552K 2
mapped file 51.0M 23
shared memory 16.4M 11
=========== ======= =======
TOTAL 3.2G 969
TOTAL, minus reserved VM space 3.1G 969
And finally, there's another 'DumpGPURestart' that looks more or less like the previous one. (There's much more text in these logs, but I thought this might be too much to share already.)
It was 'off' so I turned it 'on'. I got the same crashing behavior.
I tried turning it back to 'off'. Not surprisingly, same crashing behavior.
Just to see what would happen, I tried turning on/off/on some of the other video settings like VSync, View Bobbing, Mipmap Levels, etc.
Nothing changed the crashing behavior: No matter whether it was off or on, any version from 1.8 or later crashed.
Talking with Apple was helpful in so much as they indicated they have not heard anyone having the problems I'm having with Minecraft and they were "...reasonably certain..." Mac users were playing Minecraft on Macbook Pros running El Capitan.
This is consistent with my Googling for problems with Minecraft and El Capitan which doesn't reveal anything beyond the issue when Apple stopped including Java with its OS some versions back but the latest Minecraft Launcher fixes that problem. For example, here's a Youtube video that discusses the new Launcher running on El Capitan using Minecraft 1.8.8:
I haven't found anything related to 1.8 or later versions of Minecraft not running on El Captian MBP's except 1 post here:1.8 Not working on El Capitan that was even close. (And that post didn't offer a real solution. The solution it did offer, to install the legacy Java 6 runtime (https://support.apple.com/kb/DL1572?locale=en_US) didn't work when I tried it.)
Hi. I'm relatively new to Mac OS X and Minecraft. I've been playing Minecraft for a year+ on an old Macbook Air (Mavericks) with no problem. I just got a new Macbook Pro with El Capitan (10.11) and discovered it won't run anything beyond 1.7.10. If I try 1.8 or higher, it builds the world, drops me in, I might hear a pig snort, and then it crashes. Any version from 1.7.10 seems to work just fine. (I didn't try every one). With the new MBP, I downloaded a new copy of the Minecraft Launcher (version 1.6.61). I feel like I'm doing some simple thing wrong, but I can't figure it out.
Any help greatly appreciated,
CreeperGirlMC
we can't either. not without the actual crash log.
Sorry.
Here's what's in 'latest.log':
Here's the output from the 'Game Output' window:
Is there other useful output I should include?
(Pardon my ignorance.)
Other than the atrocious formatting these logs don't show anything going wrong in the part you've provided.
That's why I'm reaching out here. I can't find anything that I'm obviously doing wrong nor can I find anything in a log anywhere that tells me something has gone wrong. Can you point me where I might look or is there something I might have missed somewhere? Is there another log that is more informative? Is there some installation step I'm overlooking that's required for El Capitan? Where am I going wrong?
I'm not a Mac user so I don't really know about Mac specific issues.
Usually a Java exception is created and logged which points at a specific cause.
The three biggest issues that create version specific failures are (1) minecraft save data incompatibilities between versions [this generally doesn't cause a crash] (2) minecraft option / settings incompatibilities between versions [ this generally causes a Java exception of some kind] (3) changes in the way minecraft uses the Open GL APIs hitting bugs in the video driver that were always there waiting to be encountered. [ this generally causes a Java exception]
Other problems usually affect all versions of minecraft equally.
If the minecraft window just goes *poof* and disappears then the JVM is terminating in an abnormal fashion... are there any Mac specific places you can look for process failures? an event log, /var/log/messages or whatever?
Hey gerbil. I did some snooping and found a system console that I cleared out and then watched as I ran Minecraft using version 1.8 that causes the crash (and the crash goes like this: minecraft launches, the world begins to build, I am dropped into the world, I begin to hear music, then it freezes, after a few seconds...maybe 10 or less, it crashes back to the Launcher).
Buried in this log report I found an entry: 'DumpGPURestart'
It goes on for pages. Looks like address : value pairs, registers and their values, and hex dumps (I think).
Further along, I came across 'java crash report': (this I include in its entirety--it's long)
And finally, there's another 'DumpGPURestart' that looks more or less like the previous one. (There's much more text in these logs, but I thought this might be too much to share already.)
Does this give you any clues to a fix?
Thanks so much for taking the time to help,
GreeperGirlMC
Okay, thanks
One of the differences between 1.7.10 and 1.8 that you have reminded me of, is the VBO option.
Try changing it from ON to OFF or vice versa.
It was 'off' so I turned it 'on'. I got the same crashing behavior.
I tried turning it back to 'off'. Not surprisingly, same crashing behavior.
Just to see what would happen, I tried turning on/off/on some of the other video settings like VSync, View Bobbing, Mipmap Levels, etc.
Nothing changed the crashing behavior: No matter whether it was off or on, any version from 1.8 or later crashed.
Talking with Apple was helpful in so much as they indicated they have not heard anyone having the problems I'm having with Minecraft and they were "...reasonably certain..." Mac users were playing Minecraft on Macbook Pros running El Capitan.
This is consistent with my Googling for problems with Minecraft and El Capitan which doesn't reveal anything beyond the issue when Apple stopped including Java with its OS some versions back but the latest Minecraft Launcher fixes that problem. For example, here's a Youtube video that discusses the new Launcher running on El Capitan using Minecraft 1.8.8:
I haven't found anything related to 1.8 or later versions of Minecraft not running on El Captian MBP's except 1 post here:1.8 Not working on El Capitan that was even close. (And that post didn't offer a real solution. The solution it did offer, to install the legacy Java 6 runtime (https://support.apple.com/kb/DL1572?locale=en_US) didn't work when I tried it.)
I'm at wit's end.
I appreciate you sticking with me on this.
Does this apply to you: https://www.apple.com/support/macbookpro-videoissues/
Also found lots of people with MBPr and hanging GPU problems via Google, one suggestion:
"On MacBook Pros with dual GPU you can avoid the problem by disabling Automatic Graphics Switching (System Preferences > Energy Saver)."
Regarding the link: No that does not apply to my MBP.
Similarly, my MBP does not have the dual GPUs that can be switched.
I took the MBP back to the Apple Store.
I got another one.
Guess what? It works!
Thanks so much for your help. I would not have suspected anything wrong with the hardware had you not clued me into the graphics stuff.
Thanks again!
Great! all kinds of laptops in general seem to be less than 100% reliable these days.