[Feedback Needed] WoW Crashing on connect under macOS Sonoma (14.0)

The reports for this are scattered across many different threads and very few of them (if any) have hardware info. This issue seems to only affect certain macs and not all macs running 14.0 so we need more feedback to narrow down scope of which hardware specifically is affected by it.

What we know.

  1. This crash only affects users on MacOS Sonoma NOT running apple silicon
  2. This crash also doesn’t affect ALL intel users. I’ve seen at least two recent AMD/intel macs using AMD 6x00 gpus who can play fine.
  3. The crash happens near instantly on launch/connecting

What we don’t know:
Everything else (literally any hardware details of people affected by crash). Please don’t just say “imac” since that is vague. We need year, and what gpu is in it too cause even with year there are multiple gpu configurations for some years.

9 Likes

I am on a 2020 Macbook Pro and upgraded to 14.0 today - Wrath Classic and Classic Era are crashing for me on startup. This occurs both when I start from the bnet client and when I try to launch the game manually from my applications folder. For me at least, I do not even see the “Connecting” message before the game has crashed.

Processor: 2 GHz Quad-Core Intel Core i5
Graphics: Intel Iris Plus Graphis 1536 MB

Going to downgrade to Ventura for now and follow this thread.

1 Like

Same here. Game ran perfectly until I upgraded to Sonoma.

2019 Mac Pro 1.4GHz Quad-core Intel Core i5
Intel Iris Plus Graphics 645 1536MB
8GB 2133 MHz LPDDR3

2 Likes

Same.

2020 Mac Air 1.2 GHz Quad-Core Intel Core i7
Intel Iris Plus Graphics 1536 MB
16 GB 3733 MHz LPDDR4X

1 Like

This happens to me. Every time. The only information I will provide on a public forum is the following:

13-Inch 2020 MacBook Pro
Processor: 2 Ghz Quad-Core Intel i5
Graphics: Intel Iris Plus Graphics 1536 Mb
RAM: 32 GB 3733 Mhz
macOS: Sonoma 14.0

A brief stack trace is below. I am willing to supply my spx file and any client-side logs you wish - reach out to me from an official Blizzard email address and I’ll reply with the information. As a side note, I already supplied this information when I opened ticket US94478532. It was attached when I opened that ticket.

Here is the error thread:


Crashed Thread

Exception.Assertion:
Thread 0x00000103 [Stack Base: 0x00007FF7BFC21000 Used Space: 4312/67104768 bytes]
0 0x00007FF810BE491D “libobjc.A.dylib” objc_msgSend + 29
1 0x0000000102901E5B “com.blizzard.worldofwarcraft”
2 0x00000001028DDA52 “com.blizzard.worldofwarcraft”
3 0x000000010038C687 “com.blizzard.worldofwarcraft”
4 0x000000010038DCC5 “com.blizzard.worldofwarcraft”
5 0x00000001028DE10A “com.blizzard.worldofwarcraft”
6 0x0000000102977290 “com.blizzard.worldofwarcraft”
7 0x00000001029587AA “com.blizzard.worldofwarcraft”
8 0x00000001002E2207 “com.blizzard.worldofwarcraft”
9 0x00000001002E20C7 “com.blizzard.worldofwarcraft”
10 0x00007FF810C263A6 “com.apple.darwin.ignition” start + 1942
<:Exception.Assertion>


Assertion

Exception Raised!
App: /Applications/World of Warcraft/retail/World of Warcraft.app/Contents/MacOS/World of Warcraft
Error Code: 0x85100086
Exception: EXC_BAD_ACCESS
Description: KERN_INVALID_ADDRESS at 0x0000197355570E58


Registers

   rax : 0x00006000032D0E40       rbx : 0x00007FF7BFC202E0       rcx : 0x00007FF7BFC1FFD0       rdx : 0x00007FF7BFC1FF30       rsi : 0x00007FF830CF990A
   rdi : 0x00006000032D0E40       rbp : 0x00007FF7BFC20080       rsp : 0x00007FF7BFC1FF28        r8 : 0x0000000000000010        r9 : 0x0000000000000049
   r10 : 0x0000197355570E40       r11 : 0x00007FF830CF990A       r12 : 0x00006000032892C0       r13 : 0x0000000000000010       r14 : 0x00007FB450AE30A0
   r15 : 0x00007FF810BE4900       rip : 0x00007FF810BE491D    rflags : 0x0000000000010202        cs : 0x000000000000002B        fs : 0x0000000000000000
    gs : 0x0000000000000000

 mxcsr : 0x00001FA7 mxcsrmask : 0x0000FFFF

  xmm0 : 0x00000000 0x00000000 0x00000000 0x00000000      xmm1 : 0x00000000 0x00000000 0x00000000 0x00000000
  xmm2 : 0x00000000 0x00000000 0x00000000 0x00000000      xmm3 : 0x00000000 0x00000000 0x00000000 0x00000000
  xmm4 : 0x00000000 0x00000000 0x00000000 0x00000000      xmm5 : 0xEA000000 0xB4000000 0x9E000000 0x14000000
  xmm6 : 0x00000000 0x00000000 0x00000000 0x00000000      xmm7 : 0x00000000 0x00000000 0x00000000 0x00000000
  xmm8 : 0x00000000 0x00000000 0x00000000 0x00000000      xmm9 : 0x00000000 0x40968000 0x00000000 0x00000000
 xmm10 : 0x00000000 0x00000000 0x00000000 0x00000000     xmm11 : 0x00000000 0x00000000 0x00000000 0x00000000
 xmm12 : 0x4418C71D 0xBF800000 0x00000000 0x80000000     xmm13 : 0xC418B8E4 0x43C7FB37 0x00000000 0x00000000
 xmm14 : 0x00000000 0x00000000 0x00000000 0x00000000     xmm15 : 0x00000000 0xC8C36B0D 0x00000000 0x00000000

================================================================================

<Exception.IssueType> Exception
Crash
Exception.Summary:
ERROR #134 (0x85100086) KERN_INVALID_ADDRESS at 0x0000197355570E58
EXC_BAD_ACCESS
<:Exception.Summary>


Info stack for thread with exception (232345600)

So far everyone is on Iris pro. anyone crashing on anything else?

I’m using a 2019 Intel Iris Plus MacBook Air. I have Sonoma installed.

Do you know what GPU it has? if you go to apple menu and while holding option key choose “system information” you can then go to graphics/display and get that info

EDIT, you added GPU after I quoted :D. good stuff So another Intel Iris.

Thanks for looking into this! Really appreciate it.

I’m on a 2020 m1 MacBook Air 13 inch

1 Like

Hey all,

We are tracking this issue to try and figure out what is causing it with macOS 14 Sonoma. When you reply please make sure to include Mac model / year and include the graphics device.

Please also include one unique crash code (the long string of letters and numbers) from any of the WoW crash pop-ups that are showing up. This will let us look up the crash on our end and gather more info that way.

Thanks!

7 Likes

Thank you! I’m on a MacBook Air 2020, 13 inch. Graphics are Intel Iris Plus Graphics 1536 MB

1 Like

Also I can’t provide you guys with a crash log. I’ve gotten the Blizzard Error though. So I’m hoping that’ll help

Im on a 2020 Macbook Air with intel Iris Plus Graphics and updated to Sonoma 14.0 last night.

I’ve been trying every now and then since last night, I click the launcher and it takes me directly into the video for Dragonflight, then takes me to the connecting screen. Then crashes. The error code I got most recently is
6E504ECC-E4A1-4892-BFC2-BEBE75BD45F2.

Here’s my unique crash code: 135F8EB6-89F3-4D88-8030-89DFA875DD9D

Reposting specs from above:
2020 Macbook Pro
Graphics: Intel Iris Plus Graphics 1536MB

1C241C7A-FFBC-448D-88DF-A00D472513B5 for my issue. This was also provided when I opened up the support ticket.

MacBook Pro 13-inch, 2018, Four Thunderbolt 3 Ports 2.3 GHz Quad-Core Intel Core i5
Intel Iris Plus Graphics 655 1536 MB 16 GB 2133 MHz LPDDR3

WotLK Classic runs fine. Retail will run for 30 secs to 2 mins then freezes the entire computer. It restarts automatically on that. No codes that I can find to post either. Wow retail runs fine on my old iMac2015.

1 Like

6F855343-5E40-42B8-B49D-B2B36442E11F
that code when it crashes

graphic iris plus, 2020 retina macbook air

I’m unable to login, I launch the bnet app, click play for wrath classic. It’s stuck trying to do something, but WoW never launches. I tried to bypass the launcher and launch wow itself, but the icon never acknowledges my click, so nothing happens.

I’m on a MacBook Pro 2019 15 inch, 2.3 GHz 8-Core Intel Core i9, Radeon Pro 560X 4GB, Intel UHD Graphics 630, 16 GB 2400 MHz DDR4

this is now happening to me too, and I’m on apple silicon. I think this may be a different, unrelated bug :expressionless: