Mojave 10.14.1 Beta (18B50c) bricks WoW!

Mac Technical Support
Why are people using beta releases of macOS if they apparently don't understand what that actually entails?
10/08/2018 04:36 PMPosted by Bakersfield
Mojave 10.14.1 Beta 3 resolved nothing in my setup. Glad to hear it somehow works for you.


ah man... I'm really sorry about that.
10/08/2018 04:59 PMPosted by Incaely
Why are people using beta releases of macOS if they apparently don't understand what that actually entails?
Because Apple (and Microsoft) make it stupidly easy to enroll in their public beta programs and some see that as an opportunity to be on the bleeding-edge without understanding the repercussions of running beta software on production devices.
10/08/2018 04:59 PMPosted by Incaely
Why are people using beta releases of macOS if they apparently don't understand what that actually entails?


Because many actually do understand what that entails, and are trying to provide a service to this community as well as Blizzard's game developers.

It's unrealistic to expect Blizzard to be able to test for every potential bug in-house, or to limit player testing only to PTR. Community members with the willingness and ability to run macOS beta software can provide invaluable advance notice to Blizzard of potential game-breaking issues.

Like the one this thread discusses.
I also hit the same issue, but my system version is Mac OS X 10.13.6 (17G65).
How to fix it ?

Process: World of Warcraft [1397]
Path: /Applications/Entertainment/*/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 [1397]
User ID: 501

Date/Time: 2018-10-17 09:07:17.478 +0800
OS Version: Mac OS X 10.13.6 (17G65)
Report Version: 12
Bridge OS Version: 3.0 (14Y664)
Anonymous UUID: 3A84FAC1-E0D6-8B4B-426F-4028D542C373

Time Awake Since Boot: 80 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 [0]

Application Specific Information:
/usr/lib/libpreload.dylib
10/16/2018 06:09 PMPosted by Bée
I also hit the same issue, but my system version is Mac OS X 10.13.6 (17G65).
How to fix it ?

It's obviously not same issue. Create a new thread and post the FULL crash report not just top of it.
My 2017 MBP encouraged me to update to "macOS Mojave 10.14.1 (18B75)" with it's new System Preferences/Software Update window and this is where I am having almost immediate freezing of the WoW Client. Is there a "(18B75c)" that may fix this for me? If so, how could I access it if that same System Preferences/Software Update window is saying that I'm up to date?
The issue described in this thread didn't make it into final release of 10.14.1. it was a specific opencl crash that's completely unrelated to what you're seeing. you're likely getting the spaces freeze that's been around since 10.14.0 which has work arounds if you look at other threads.

Join the Conversation

Return to Forum