I’ve noticed lately that World of Warcraft will continue to run in task manager after I exit the game and the only way to actually stop it is to end the task. This was not an issue in DF.
I’ve also noticed WoW causing considerably more heat to be produced that in DF on my CPU.
Anyone else noticing this or know why this may be happening?
I was not able to replicate this myself. The Agent process monitors for updates in the background, so that might be the cause.
Old thread but I’ve been having this issue as well, Started maybe a week after TWW launch.
My fans ramp up massively and cpu temps shoot from 55-60 where they sit with the game running for awhile to 75-80~, Cpu load is only ever around 30-40% when it does this.
The only way to stop it is by closing wow, and either waiting a min for it to finally go away on task manager (stays active in task manager for a min or two after closing) or ending task manually, and then when I restart game temps go back to normal and stay that way until it does it again (can take hours to days).
Only does this with WoW, no other program.
That’s funny cause I’m having the same issue, but it started first with Overwatch. Now WoW is doing it too. It’s incredibly annoying. Funny how the only 2 games I’ve ever experienced this issue with are both Blizzard titles.
I never did find a fix for it… Sometimes it closes fine, other times I have to go into task manager and close it, so who knows… I’ve also has issues closes Diablo 4 since the new xpac launched, which yeah, like you, 2 Blizzard titles, but no other game has this issue.
While my WoW closes in like 2 seconds, after clicking quit in the game, I kind of remember testing/looking into this for OW2 ages ago; where it takes like 5-10 seconds to close completely. The only real conclusions I could come up with(without using external tools that might break the ToS) were that it was either a Windows memory management issue(in how it handles freeing ram) or some kind of anticheat engine thing.
It will show a little bit of disk usage while it’s closing, so it’s possible that it’s doing some kind of hashing on the loaded assets and saving some kind of data to the ntfs journal or something to compare on the next boot to see if anything has been tampered with. It also creates some *.lru file in the wow\data\data folder on close, so that adds some further evidence to what I’m saying. But when I hear LRU, I immediately think of “least recently used,” so it could just be some caching thing.
They are one of the few big name online gaming companies that only use user-level anticheat engines. Valve’s VAC has a lot of weird idiosyncrasies as well(contrary to conflicting info you might read online about it, it’s not a kernal level anticheat and operates at user level).
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.