TWW prepatch has been causing my game to crash - I get the spinning ball of death almost exactly 30 seconds after login and the game crashes. Using an M3 Macbook Pro. Anyone else experiencing the same issue can shed some light on this?
3 Likes
I am also on an M3 MacBook Pro. My game isn’t crashing in the same way, but so far I have found two instances it does crash 100% of the time. Trying to set a smoke bomb for a quest in Hellfire Peninsula, and trying to talk to an NPC at the top of the Violet Tower in Netherstorm to turn in a quest. I can repeat both 100% of the time.
Wasn’t able to reproduce those issues on M3 Max Macbook pro. are you getting crash reports? might help to post one (can find them in errors folder within wow folder if they happened)
I’ve dug around the folder and can’t find any sort of error logs in it. Tried reinstalling, but the same issue persists. Sometimes it’s 30 seconds, sometimes it’s 30 minutes, but eventually the game will always freeze, give me a spinning ball and close itself without explanation.
2 Likes
Having the same issue, Atlaa, and I haven’t been able to find error logs either.
Same issue but with an M2
How much memory do you all have?
My mac specs are:
Processor: 1.4 GHz Quad-COre Intel Core i5
Graphics: Intel Iris Plus Graphics
Memory: 8 GB 2133 MHz
On Sonoma 14.6, unfortunately upgraded recently and this might be part of the issue.
crashes constantly, flying and checking mounts collection and crash. Happens often
2 Likes
for the me the game isn’t crashing its just disconnecting every 30 seconds sending me back to reconnect to the character select screen. I’m running m3 pro with 18gb memory. Haven’t checked crash logs yet and I’m about to try 0 add ons and see if it persists
Similar here. Was working fine earlier today, but on an M2 Ultra, this evening, I keep disconnecting whenever I try to attack anything. Or interact with an NPC.
Macs with intel Iris will do nothing but crash on macOS 14.x due to regression in driver. there is no fix for that, except go back to macOS 13.
The others crashing on apple silicon need more information on macs
Those who have disconnect issues, make a new thread, it’s not same issue
1 Like
That’s unfortunate — thanks for letting me know. Looks like I’ll either need to upgrade to another laptop or quit for a bit!
Update: No error logs were ever found in my game files to share, and the crashing has been minimized to once every several hours. If it adds any context, the only way I’ve found to manually trigger a similar crash is to resize the game from fullscreen to windowed - spinning ball & crash every time.
Also experiencing this- since the warband update. Freezing randomly- flying, when a new even spawns, moving the camera.
This is what I’m getting, it seems to be graphical, happens when menus pop open or quest speech boxes during certain scenes happen. Freeze and get the wheel then desktop. Happened multiple times today
<Exception.IssueType> Exception
Crash
Exception.Summary:
EXC_BAD_ACCESS: KERN_INVALID_ADDRESS at 0x00000000000000A0
19 crashes today.
All reported in my error folder
I use a Apple Mac mini M2 Pro
I have lots of memory available
& run with the latest sonoma update
These crashes occur from when I am flying in Normie Druid Mode,
dragon style, Pet battling, or flying in-game in Shadowlands-
or from when I am just walking about in the game.
but happen mostly when I am interacting with a “mode of transport.”
The most recognizable of a crash, so far,
is when I am using the flight master in Shadowlands-
the NPC flying mount is “funny looking” and not fluidic.
then, the environs will start to look very Blocky- and then:
rainbow wheel, & BONK.
{queue that Dave Mathews song}
my assorted error messages range from the ones people have posted above,
to long lines of coded Complaints and Gripes with the phrase,
> Adding server node 22. Server 'us.cdn.blizzard. com
And then another one a lot like it, but with slightly different numbers, repeated 20 times
its very reminiscent to crashes experienced in BFA, but with more irritation, because I have a fancy Mac, have never had “lag” and it reminds me of the Intel one.
And those were some dark days of crashing
just from using on a glider?
You didn’t by chance at some point during an install or patch cycle click the Play button before said cycle was 100% finished did you? That sounds an awful lot like the game is attempting to download something which it will only do if you didn’t let it finish installing before playing at some point and the client corrupted your game files as a result.
no- my first time logging on this week was yesterday
Its unplayable. Crashes every 5-10 minutes.
8/5 13:45:48.376 LogOpen
8/5 13:45:48.376 World of Warcraft Retail ARM64 11.0.0.55939
8/5 13:45:48.376 macOS 14.5.0 (23F79) arm64
8/5 13:45:48.376
8/5 13:45:48.376 Apple M1 Pro | Sockets:1 Cores:10 Threads:10
8/5 13:45:48.376 32.0 GB System Memory
8/5 13:45:48.376 On AC Power - Battery Present (100%)
8/5 13:45:48.377 Adapter 0: “Apple M1 Pro” family:Unknown type:Integrated location:0 driver_date:02-May-2024 driver_ver:(0x0) vendor:0x106b device:0x0000
8/5 13:45:48.377 Monitor 0 “(null)” Size(1920x1080) Pos(0, 0)
8/5 13:45:48.377 Choosing low power gpu: “Apple M1 Pro”
8/5 13:45:48.377 Compat Settings: Disable Opt Features:false, Disable Device MT:false, Disable Cmdlist MT:false, Disable work sub optims:false, Disable async frame end:false
8/5 13:45:48.377 GpuInfo: sm:mtl_1_1, rt:None, vrs:0, bary:0, mesh:0 pull:1
8/5 13:45:49.152 NotifyOnDeviceCreate
8/5 13:45:49.153 Metal Device Create Successful
8/5 13:45:49.153 Using shader family mtl_1_1
8/5 13:45:49.153 UAV format support RGBA8:true BGRA8:true RG16F:true RGBA16F:true
8/5 13:45:49.153 No
8/5 13:45:49.153 Detected Graphics Defaults: 5 (CPU = 7, GPU = 5, MEM = 7) WindowSize: 1920x1080
8/5 13:45:49.153 GxLowLatencyMode: None
8/5 13:45:49.257 Render Settings Changed. New Render Size: 1919x1151 (1800x1080 @ 106.7%)
8/5 13:45:49.257 GxLowLatencyMode: BuiltIn
8/5 13:45:50.119 Render Settings Changed. New Render Size: 1919x1095 (1800x1027 @ 106.7%)
8/5 13:45:50.123 Periodic Gpu Status Report: Mem Budget: 0.3GB / 21.3GB (1.2%)
8/5 13:46:05.746 Render Settings Changed
8/5 13:47:30.581 Render Settings Changed
8/5 13:47:36.202 Crash Summary: EXC_BAD_ACCESS: KERN_INVALID_ADDRESS at 0x00000000000000A0