Omegal, unfortunately it happened again without addons.
My setup:
macOS Monterey - Version: 12.6.1 (21G217)
Mac mini (2018)
Processor: 3,2 GHz 6-Core Intel Core i7
Memory: 32 GB 2667 MHz DDR4
gx.log
10/26 21:17:26.017 LogOpen
10/26 21:17:26.017 World of Warcraft Retail x86_64 10.0.0.46313
10/26 21:17:26.017 macOS 12.6.1 (21G217) x86_64
10/26 21:17:26.017
10/26 21:17:26.017 Intel(R) Core(TM) i7-8700B CPU @ 3.20GHz | Sockets:1 Cores:6 Threads:12
10/26 21:17:26.017 32.0 GB System Memory
10/26 21:17:26.017 On AC Power - Battery Not Present
10/26 21:17:26.023 Adapter 0: "Intel(R) UHD Graphics 630" family:Gen9_5 type:Integrated vendor:0x8086 device:0x3e9b driver(0x0) location:0
10/26 21:17:26.023 Monitor 0 "LG ULTRAWIDE" Size(2560x1080) Pos(0, 0)
10/26 21:17:26.139 Choosing low power gpu: "Intel(R) UHD Graphics 630"
10/26 21:17:32.592 Error Loading Shader: 3186452
10/26 21:17:32.611 NotifyOnDeviceCreate
10/26 21:17:32.614 Metal Device Create Successful
10/26 21:17:32.614 Using shader family mtl_1_1
10/26 21:17:32.614 <IsGPUDriverOutOfDate> No
10/26 21:17:32.614 Detected Graphics Defaults: 2 (CPU = 7, GPU = 2, MEM = 7) WindowSize: 1920x810
10/26 21:17:32.614 GxLowLatencyMode: None
10/26 21:17:32.829 Render Settings Changed. New Render Size: 1536x648 (2560x1080 @ 60.0%)
10/26 21:17:36.418 Render Settings Changed
10/26 21:18:27.116 Metal Device Destroy
10/26 21:18:27.116 NotifyOnDeviceDestroy
10/26 21:18:27.166 GxShutdown
New theory has been found.
Try adding this to config (while game is closed)
SET GxAllowCachelessShaderMode “0”
see if you can reproduce leak
I’ve been having the same, my mac crashes completely when it hits about 86.5gb of ram used from WOW
Was going well at between 8-10GB of memory, but then started to increase, got to about 40 and I exited WoW
Yeah, still have no idea what’s causing it, i have had wow open for 8 hours. memory is at 4GB, i can’t reproduce it.
As mentioned above, it only occurred when I moved from the WoW window.
I have WoW on a dedicated Space, and switch to my main space when checking Wowhead or waiting on something like a flight path are queue
When I didn’t move from that Wow window, I had no issue yesterday.
Omegal, new information.
I tried to play with a fresh install without addons, and the game gave the same error, reaching 129GB of memory.
I got an id from the report: 8DBA35BD-773D-4058-9F9C-4A8F7B49D7A8
After that I tried with the option SET GxAllowCachelessShaderMode “0”, and the same error. Unfortunately, macOS did not generate an error report.
I’ve noticed, too, that this happens when switching “virtual desktops” or CMD+TAB’ing to different windows. When staying within the Wow.app, things seems fairly stable between 4-8 GB memory.
I turned off all addons and updated my Config.wtf file with SET GxAllowCachelessShaderMode “0”. It still breaks when changing windows/desktops over time.
Turned on max foreground fps, I played for over an hour and the error did not happen. I switched to “virtual desktops” and CMD+TAB’ing to different windows usually.
Any news I’ll let you know.
I’ve experimented with my system and found the same thing.
If I have two or more “Spaces” active, and I switch away from the Space containing WoW, WoW’s memory usage increases very quickly.
If all apps are in the same Space (even if WoW is full screen), I can switch between apps without WoW’s memory usage rising above 6GB.
It happened to me on Beta and PTR, but not on Live. They fixed it on both Beta and PTR and now it’s happening again on Live. Very odd!
I don’t think it was ever fixed, it just requires several things at once to happen. We’re narrowing it down but definitely think it’s related to 2 or more spaces or screens, uncapped fps, and ventura
We’re working on getting a client deployed that will have additional memory logging to try to narrow down where this memory is coming from. So far, I haven’t been able to reproduce this issue internally, still trying though.
3 Likes
I’m not on Ventura yet. But I am playing with an external monitor on my MacBook Pro - almost exclusively with the main screen closed. Sometimes I limit foreground frame rate to keep my fans off, sometimes it’s uncapped. I don’t have the target frame rate checked.
I have vsync on and capped at 60
Wish there was something we could do which would help log things
Is there any way to export what are settings are when we have the issue?
I’m running Monterey (12.6.1) with 64GB of real memory on a Mac Studio. Activity Monitor is running in the background. All addons are turned off. Starting the game initially uses 3-4 GB of memory. Loading a toon sitting in Stormwind (doing nothing) experiences the increased memory usage slowly (minutes to get over 10GB). Quitting and restarting the game (to release the memory) and then loading a toon sitting in Oribos (doing nothing) consumes memory much more rapidly (less than a minute to get to 50GB). Command-tabbing to another application or the desktop accelerates the memory leak in both situations. This is repeatable.
My testing shows the leak happens with the following componants
spaces are used, foreground fps cap disabled, vsync on, and hiding wow window when in other space.
all of them required, any of them not there, leak doesn’t occur for me
My experience was initially as yours; foreground fps off, vsync on, hiding WoW, switched to another app. I just tested with the Oribos character and changed one variable and turned vsync off. The formerly rapid memory climb slowed similar to the SW toon. However as soon as I switched to another app/hid WoW, I hit 160GB memory use and crashed in less than a minute. This was with vsync off. So there are definitely some variable symptoms in this problem.
Was able to reproduce with 100% probability, steps described here
1 Like