Since the patch today, the client has crashed several times. I was doing regular quests, a delve and was just about to start the bridge scenario when it again crashed. I get the spinning color ball, client becomes unresponsive and then closes, leaving me with the crash report window. I fill it out and submit it. I am not running any add ons. Im on the most current version of MacOS, nothing else running, and before this patch, the WoW client has been super stable with no issues. Any ideas on what could be causing this, or is it just typical patch bugginess that we have to wait to be fixed because you rushed the patch out? Thanks!
12 Likes
Same issue here. Hopefully it’s a general issue and not just a Mac issue or we might not se e it fixed for a while.
For me it happens pretty much all the time. Unplayable currently.
9 Likes
Same here. I keep crashing. I crashed 5 times trying to do Decor Duel.
2 Likes
For me it seems like I crash when I go into combat.
Disabled all addons it’s not crashing as much so it might be an add-on that is influencing the issue.
After the maintenance will retest it all with everything disabled then add them on till I find the culprit.
2 Likes
Not sure if this is everyone’s issue but I am using unhalted unit frames and another add-on with it to remove the world buffs called “UUF World Buff Filter” and when I removed that one it stopped giving me my automatic combat crashes.
I am not sure if this will fix everything for me but that worked at least for now was able to get started on the patch at least.
2 Likes
This is happening with me too when I join a battleground – it loads fine, then after about 5 seconds or so, the game becomes unresponsive, I get the spinning beachball, then it completely crashes.
2 Likes
Getting consistent crashes entering Epic Battlegrounds (beach ball then hard close) on Mac.
Clean WTF, no addons, reproduces every time.
Crash log shows EXC_BAD_ACCESS: KERN_INVALID_ADDRESS (Error #132). Two issues visible in gx.log pointing to a build regression:
-
After a graphics restart, half-float texture formats (RG16F/RGBA16F) drop to
falseandOPT_FEATURESgets disabled — they should stay enabled on this hardware. This affects lighting/SSAO/volumetric fog and likely causes instability. -
After the app goes background/foreground, the Metal GPU memory budget corrupts to a garbage value (~17TB reported against a 28GB budget). The game then enters the most memory-intensive zone type with broken memory accounting.
Worked fine before 67088. M3 Max, macOS Tahoe 26.4.1, Retail ARM64.
4 Likes
Getting the same error in raids (Voidspire). Constantly crashes with this in gx.log:
4/22 15:44:45.575 Mapping thread ID 61795 as 1
4/22 15:44:45.575 [1] Crash Summary: EXC_BAD_ACCESS: KERN_INVALID_ADDRESS at 0xA9CBDFE25771D470
2 Likes
So far after disabling the above add-on I mentioned I have had no crashes at all and did some M+/bgs.
There are a ton of addons though causing lua errors and such and some other weird particulars but not the crashes I had upon the patch launch.
So best advice is to make sure to check all your addons 1 by 1 and see if you can fix it that way although I am sure it’s possible it’s broken no matter what since some of you are reporting issues all disabled.
Confirmed the issue is with certain addons, though still means there is a in game bug as an add-on shouldn’t be able to crash the game with a memory error.
Agree, I went 1 by 1 addons…clean install. Sometimes works in BGs, sometimes crashes.
Delves/Raids too. It’s really hard to pinpoint wtf is making sh*t crash. Didn’t check M+s tho.
Something is really wrong with Mac mem allocations…And guessing they won’t fix it for weeks….betting their AI/Interns don’t even know how to fix it. Sad.
a new build just rolled out -12.0.5.67186.
hopefully that fixes the crashes. from what little bit ive tested so far so good.
This new build fixed all my crashes. Glad it was fixed pretty quick for a client side issue