Mojave 10.14.1 Beta (18B50c) bricks WoW!

Mac Technical Support
MacOS Mojave 10.14.1 Beta (18B50c) bricks WoW. Confirmed.
Confirmed. After upgrading to macOS 10.14.1 Beta (18B50c), Wow crashes to desktop.
Damn, confirmed as well. My Mac autoupdated to it too
I can't believe I was fine all through the Mojave beta, and now it breaks WoW on the 2nd beta of a .1 update.
Latest WoW patch 8.0.1.27980 still brings No Joy; WoW crashes to desktop.
Don't forget to send crash reports to support. They can always use them.
Same here!
Same here cant play!
Chiming in to confirm here as well.

Running on a MacBookPro15,1 with 4GB Radeon Pro 560X discrete graphics.
WoW launched normally on macOS 10.14 and on 10.14.1 beta 1, but after updating to 10.14.1 beta 2 yesterday, WoW crashes on launch. Looks like they changed something with the OpenCL framework that WoW isn't too happy with.

Here's the relevant stack trace:
Process: World of Warcraft [52451]
Path: /Applications/World of Warcraft/World of Warcraft.app/Contents/MacOS/World of Warcraft
Identifier: com.blizzard.worldofwarcraft
Version: 8.0.1 (8.0.1.27980)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: World of Warcraft [52451]
User ID: 501

Date/Time: 2018-10-04 13:26:57.592 -0400
OS Version: Mac OS X 10.14.1 (18B50c)
Report Version: 12
Bridge OS Version: 3.0 (16P51048a)
Anonymous UUID: 8D2B7B8E-4076-A445-B9DD-09F12AB5EEAF

Sleep/Wake UUID: 3AEEA172-A3FA-4906-A223-10787F7EDB82

Time Awake Since Boot: 51000 seconds
Time Since Wake: 51000 seconds

System Integrity Protection: enabled

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_INSTRUCTION (SIGILL)
Exception Codes: 0x0000000000000001, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY

Termination Signal: Illegal instruction: 4
Termination Reason: Namespace SIGNAL, Code 0x4
Terminating Process: exc handler [52451]

Application Specific Information:
/System/Library/Frameworks/OpenCL.framework/Versions/A/OpenCL
I'm having the same problem. Thanks for the info.
Same
Process: World of Warcraft [462]
Path: /Applications/World of Warcraft/World of Warcraft.app/Contents/MacOS/World of Warcraft
Identifier: com.blizzard.worldofwarcraft
Version: 8.0.1 (8.0.1.27980)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: World of Warcraft [462]
User ID: 501

Date/Time: 2018-10-04 16:10:56.151 -0700
OS Version: Mac OS X 10.14.1 (18B50c)
Report Version: 12
Anonymous UUID: 3E84FDA4-2B15-B434-55C6-F6C218D0EB2D

Time Awake Since Boot: 34 seconds

System Integrity Protection: enabled

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_INSTRUCTION (SIGILL)
Exception Codes: 0x0000000000000001, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY

Termination Signal: Illegal instruction: 4
Termination Reason: Namespace SIGNAL, Code 0x4
Terminating Process: exc handler [462]

Application Specific Information:
/System/Library/Frameworks/OpenCL.framework/Versions/A/OpenCL
I'm surprised so many use beta OS versions.

It's also odd it's crashing on OpenCL. Wow doesn't even use opencl, so i'm willing to bet bug is totally apple's fault.
Same issue here.
10/04/2018 07:47 PMPosted by Omegall
I'm surprised so many use beta OS versions.

It's also odd it's crashing on OpenCL. Wow doesn't even use opencl, so i'm willing to bet bug is totally apple's fault.


I can't speak for anyone else, but I beta test for work on my laptop and keep a copy of WoW on it to test this sort of thing. My game rig runs stable releases only.
I saw someone mention on another thread, the idea of swapping the Open CL version from an earlier release. Since I was going to have to reinstall the OS anyway I figured I'd give it a shot.

I moved Open CL from 10.14 final and popped it onto the laptop, and it works! Only tested it for a few minutes though. So far no issues elsewhere either.

Probably not the most responsible thing to do. I'll keep testing and post back tomorrow.
10/04/2018 07:47 PMPosted by Omegall
I'm surprised so many use beta OS versions.

It's also odd it's crashing on OpenCL. Wow doesn't even use opencl, so i'm willing to bet bug is totally apple's fault.


At the risk of sounding like an idiot (I am, I know) I actually totally forgot I was opted in on all my machines, I normally only run the beta build on my laptop. Woke up and it had auto-installed itself already. Which also means I didn't have a pre-install Time Machine backup ready to roll it back.

Seems like I will have to wait til it either gets fixed on apple or blizzard's end and then opt-out asap.
10/04/2018 10:08 PMPosted by Gimbap
At the risk of sounding like an idiot (I am, I know) I actually totally forgot I was opted in on all my machines, I normally only run the beta build on my laptop. Woke up and it had auto-installed itself already. Which also means I didn't have a pre-install Time Machine backup ready to roll it back.

Seems like I will have to wait til it either gets fixed on apple or blizzard's end and then opt-out asap.


You could clone your boot volume to an external drive, install the previous OS onto the internal (after formatting of course), and then use Migration Assistant to move your settings/user folder to the newly installed OS and get back into action that way.

I can't stress enough the importance of having a steady backup scheme so you lose minimal time and energy reverting to a known working setup. :)
10/04/2018 09:20 PMPosted by Phreeman
I saw someone mention on another thread, the idea of swapping the Open CL version from an earlier release. Since I was going to have to reinstall the OS anyway I figured I'd give it a shot.

I moved Open CL from 10.14 final and popped it onto the laptop, and it works! Only tested it for a few minutes though. So far no issues elsewhere either.

Probably not the most responsible thing to do. I'll keep testing and post back tomorrow.


Where did you get Open CL?
Presumably the OpenCL referenced as being replaced is /System/Library/Frameworks/OpenCL.framework

Not surprising it bugs out in Mojave since Apple's moving away from any support for it at all.

Join the Conversation

Return to Forum