Periodically the game will crash hard, forcing the system to restart entirely. This has happened about 8 times since 9.2 launched, so it is an intermittent thing, but I’ve had it happen twice in the same Plaguefall M+, twice in a row (crashed as I was logging back in) in Sepulcher raid, and other times in Zerith Mortis or Sepulcher. The crash usually happens when there is a lot going on on the screen, but not every time, or else it would be unplayable. Sepulcher has crashed when I was just moving from one spot in the instance to another, following along with my raid team.
I am running Catalina 10.15.7 on a late 2013 27" iMac. Yes, I know that’s old. I have a Mac Studio coming in a week or so.
I’ve had the same exact issues since 9.2. It seems to happen in PF the second the key goes in, by the summoning stone for SoA. and the desert area of ZM. I found that launching from the client helped with crashes in dungeons but I still get crashes in ZM most of the time.
I’m also running Catalina but on a late 2017 iMac.
I have a hypothesis that I will test out, since I have experienced the same sort of crash twice now on my new Mac Studio running Monterey 12.3. I had the Screensaver set to lock the machince as soon as the screensaver acivated. If somehow the activity in WoW was not being seen by the system, and it went to screensaver, then the system switched and “saw” my inputs again, trying to prompt me to unlock, perhaps that explains the symptoms. What I see is a freeze of all activity and cursor movement in WoW, then it dumps me back to the OS login page, but it is not making the system restart chime, nor is it showing evidence of a kernel panic.
So I have set a delay between the screen saver activating and locking the system. Likewise, I will try to remember to periodically bring a background app like Discord, Safari or my raid logger to the foreground, just to keep the system active. This idea doesn’t explain why it crashed when I was loggin in immediately after a prior crash though.
That just sounds like a graphics driver crash that causes windowserver to restart. Screen savers in general can be kinda buggy with some apps, why not just disable that and set display to sleep at 5min?
also, WoW has it’s own feature that you can enable via console command to disable standby when open, I enable this precisely to avoid situations machine goes in standby if I afk in wow for a few min.
/console PreventOsIdleSleep 1
Got knocked off game . can not log back into game. First said all realms are full. Other attempts show all realms incompatible.
Is there anyway ti notify Blizzard?
\I am sure they never read these forums
I’m sure it’s a few days too late now, but incompatible realm just means your client needs an update.
Restarting your Launcher or even your computer will generally fix that.
On my Mac Studio I recently found that turning on Vertical Sync under Graphic Settings seems to have helped. Running Monterey 12.4
according to this topic: Windowed Mode - resizing quits WoW - #71 by Tholaren-nordrassil
Blizzard changed some backend WoW code with 9.2, and now it’s highly unstable in MacOS (and it’s absolutely unusable in Windowed mode). Blizz says “not our fault, it’s a bug with macOS”, even though literally NO other games or even applications bug out like WoW does. And now they’re refusing to fix this, or revert their code to the version that worked flawlessly.
Thanks, Blizz 