NOTHING Blizz suggested changed it, finally I got a wholelnew Apple computer, the game was working fine for a week, now it’s back.
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 LOL”, even though literally NO other games or even applications bug out like WoW does, which means it’s a WoW-only issue (not a macOS issue). And now they’re refusing to fix this, or revert their code to the version that worked flawlessly.
Thanks, Blizz 
2 Likes
Yes, I began to get this bug on 9.2 also… Before it worked perfectly… To make things worse, everytime I restart the computer, the game won’t even launch, I have to uninstall and install it again, it work as long as I don’t turn the computer off… But its buggy all the way…
Yep I hope Blizzard does press release on this crud!
Yep, here too
Cleaned everything Blizzard off my Mac. Cleaned Library of anything net.battle or com.blizzard. reinstalled Bnet app.
Thing now hangs on launch with 100 percent CPU usage.
My turn to experience this. And in addition to Agent taking 99% CPU for each copy of itself, it’s now constantly respawning copies of itself infinitely. It’s broken beyond reason here. Guess I get to troubleshoot this so I can figure out a workaround that might help others too.
So much for D3 PTR testing…
Edit: I got mine working. Maybe this will work for some of you. Here’s how:
- Navigate to the /Users/Shared/ folder.
- Delete the following two folders, but do not touch the Battle.net app itself:
/Users/Shared/Battle.net
/Users/Shared/Blizzard/Battle.net
- Launch the Battle.net app and let it download everything fresh. The reason for not deleting the Battle.net app along with the folders is to prevent having to use an installer that might fail on its own. This way you still have a working copy of the Battle.net app itself, but now you will hopefully have a fresh Agent and only one Agent folder (version 7893).
Have patience on the first attempt to update or install a game. It will say “Paused” once it reaches 100%. Let it do its thing and do not click Play until the “Paused” message disappears and only the game version number is beneath the Play button.
Special Note: Make sure to set the Battle.net app to close exit completely on launching a game or else you’ll have Agent sucking 100% of at least one core while you’re playing, which could turn your game into a slideshow.
Edit 2: Looks like when D3 calls Agent it keeps spawning in the background, though not at 99% per core. For those that can get into WoW (for the WoW players here with the issue) you can try getting into the game and then going into Terminal and doing the following:
sudo killall -9 AgentThis will instantly kill all processes exactly matching the name “Agent” at once. If you’ve been playing for a while and your RAM pressure is up due to swap/compressed RAM, you’ll need to restart the computer to fix that. But if Agent is eating RAM and you have not yet reached the point where compression and/or swap are used, you can simply use this command in Terminal:
sudo purgeIt isn’t a perfectly clean slate like when you restart the computer, but it frees up RAM to be used again. Ain’t gaming on macOS fun these days?
1 Like
Blizzard will probably say their code is working fine, and the bug lies somewhere in Apple’s macOS API or something 
and then (of course) not do anything to fix it, bc no one cares about Mac customers
Not here they won’t. Sadly it’s radio silence so far since it isn’t affecting Windows users. There are two issues at play here. One is the memory leak that’s happening in all macOS versions. The other is the infinitely respawning Agent processes which drags down system performance significantly. The latter appears to be potentially Intel specific as I haven’t heard any M-series users complain about that, though they might not necessarily know what or how to look for it and thus we’re missing it. But the infinite respawn doesn’t happen on Omegal’s M-series Macs so I’m inclined to lean toward a bug on the x86 portion of the platform code.
Either way, Agent is the culprit and it’s insanely borked right now regardless of which architecture is in use. I’m partially shielded from the memory leak in that I play D3 only currently which limits the damage Agent can cause, but for WoW users it’s much, much worse. The Battle.net app team has had a noticeable drop in quality over the last year. It’s frustrating too, even for a tech support specialist such as myself. I can play on the Windows side for D3, but not WoW due to the lack of a focus lock that was graciously put into the macOS client so I and others like me could continue to play WoW.
If I manage to come up with a workaround before Blizzard finally fixes the problem I’ll make sure it gets posted here ASAP. Unfortunately with how fragmented Apple’s OSes are right now (some use compartmentalized user/system volumes while others do not and the M-series Macs impose a few other restrictions as well), I wouldn’t expect one solution to be a silver bullet just yet.
1 Like
It’s also important to note that battle.net team is completely separate from any game team.
It’s also the most novice team. it’s entry through and through. That doesn’t mean they don’t know what they are doing, but more over to fact that they probably aren’t as quick or effective at it… IE a more entry coder can code something that works…ish but not as well as someone who’s learned through years of experience that while A works, B is better way to make that work, etc.
There is something to be said about experience and having all the ones with least amount of it on your patching platform has not been great for blizzard over the years, to say the least.
It looks like a silent update went out to Agent to fix the respawning issue. I’m only seeing one Agent process now and updates and patching works as expected. However, I’m on the beta branch, so if you’re on the non-beta (retail) branch, you may need to switch to beta in order to pick up the Agent update if it hasn’t been fixed on retail yet.
Edit: Nope, still borked. *headdesk*