Just posted this in another thread, posting here in case it helps blizzard troubleshoot:
I just had this memory leak crash my system while I was tabbed out of wow. The game was on another desktop space while I was using Safari for about 20-25 minutes when suddenly everything ground to a halt and I received this error message (which I had to take a picture of with my phone because the system promptly froze once I scrolled to the bottom of the list).
I’m on a Mac Studio with M1 Ultra, 64gb ram. MacOS Monterey 12.6. Here are screenshots of my graphics settings: screenshot one and screenshot two.
It looks like the test cases @Omegal suspects were true in my case as well. I was using desktop spaces, foreground fps cap was disabled, vsync was on, and the wow window was hidden because it was on another space while I was using Safari.
Build 10.0.0.46455 should fix memory leak, released few minutes ago.
1 Like
sadly still a memory leak here with my intel imac. running macos 13, capping foreground fps to 60, vsync on. starts out low but the longer the game is open the memory usage will just go up and up.
2 Likes
Yes, same here. Actually it even feels worse.
Does it rise indefinitely or is it stopping at some point that you just feel is too high?
It just rises to the point I can’t do anything. I am kinda at the point of reinstalling it. I do not have this issue on beta.
Can you be more specific though, what’s it’s memory usage at that point?
I didn’t realize I was on both forums. I answered the other one for now
This is happening to me a lot
still happening 12/26/2022
It’s going to keep happening to anyone on macOS 13.x with a mac that doesn’t support metal 3, and not a single thing blizzard can do about it. Metal 2 has a memory leak and debugging me and blizz engineer did showed that the leak i actually outside of application heap and in driver calls. Only way to avoid it is to downgrade to macOS 12 if you have a mac that is using a specific range of AMD gpus they didn’t add Metal 3 support for.
Oh, and keep battle.net closed. Agent DOES have a memory leak that’s blizzards fault still so you want to avoid letting that stay open for days at a time.
Indeed still happening. I tab in and out of WoW crafting items while watching stuff on my other monitor. After a couple hours the usage is 90%+ and my game starts lagging out and wanting to crash.
If you’re on Ventura, which it sounds like you are, and you’re on an Intel Mac that has an AMD GPU that is not supported by Metal 3 (also sounds like you are), your only option to avoid the memory leak is to downgrade to Monterey. It’s a fairly involved process though, so make sure you make a backup first.
If you are not on Ventura and you’re seeing 90%+ usage, your machine is likely overheating and you’re seeing the result of kernel_task having a dummy load put on it to throttle the CPU until it cools down. In that case, you need to clean out your Mac’s vents, or if you’re unable to do so yourself, take it to an Apple store and have them clean it out. Their Genius Bar should be able to accomodate that.
1 Like
Still happening as of 10.0.5 on an M1 Mac Mini running Monterey.