World of Warcraft - Ram = 138GB = Crash = Battery Not Charge

[TBoneMac]

Hello. Was playing World of Warcraft and suddenly the Force Quit window came up on macOS and it said wow was using 138GB of ram.

I then played a bit afterwards after resetting my computer.

Now the battery won’t keep charge. It’s from 2017 so I don’t have any sort of warranty… what should I do?


EDIT

it might be charging very slowly I’m not sure. I have it plugged in and I can use it but it’s at 1% and it’s slow To use.

EDIT EDIT

it is charging now (4% as I type this!) so that’s a relief.

I’ve had this issue for a while where my charger will be plugged in but it will say “Battery Not Charging” if I mouse over the battery icon. To fix this I usually have to unplug the charger from the macbook and sometimes from the power outlet itself and then plug back into the macbook and it then works.

So I think what happened is when I reset my PC I unplugged the charger and then plugged it back in but it was ”Not Charging” so when my battery reached 0 I got the issue that I posted here in the forums Which is a totally drained battery at 0%

 

[floral]

All that warcraft got a little out of hand...

 

[TBoneMac]

nice pun!

I’ve never seen anything take up more than about 7-8GB of ram. When I saw 138GB at first I thought it’s the amount of storage space WoW was taking up so I thought “Oh yeah 138GB that’s a lot but it kind of makes sense” then I realized it was RAM.

For reference my macbook has 16GB of ram, if I’m not mistaken.

 

[Honza1]

When battery discharges too much - and this one looks like it did - it takes some time before charging indicators normalize. It can look for long time as if nothing is happening...
This deep discharge is way to destroy the battery really quickly, the chemistry does not like this deep discharge - even though, we do not know how much spare capacity Apple keeps. I would assume system should provide ample warnings and try to prevent user from this deep discharge. If you ignored it yourself, then try not to do it to protect the battery life. If battery dropped quickly from some reasonable values to 0%, then you likely have bad battery and are looking at replacement.
Over the years few of my MBPs did have batteries, which dropped from 20-60% to 0% abruptly, within seconds. Replacement was the only option.
WoW memory leak is something else and has nothing to do with battery. If the swap file becomes 138GB, most systems will likely misbehave or die.

 

[TBoneMac]

So @Honza1 are you saying that I’m lucky that my macbook is still working after the 138GB usage of ram?

 

[TinyMito]

battery charging will slow if your laptop is very hot after playing a long gaming session

 

[Honza1]

So @Honza1 are you saying that I’m lucky that my macbook is still working after the 138GB usage of ram?

No, did not say anything like that... Restart should fix it. Memory leak of that size is beyond macOS design ;-)
The battery issue is different problem. I would check/test the battery carefully, MBPs do not run well with bad battery or without battery. They are power limited to prevent brown outs when battery is missing or not reporting to be good health. And even if it is reporting good health, it is really annoying when system shuts down due to battery dropping from 40% to 0 in seconds. Have had that on 2010 MBP, it was really annoying.
Note above about heat is great point. If WoW overheated battery, it could have provoked the drop in power. Heat is bad for batteries (as is cold and lots of other things...).

 

[dmccloud]

Hello. Was playing World of Warcraft and suddenly the Force Quit window came up on macOS and it said wow was using 138GB of ram.

I then played a bit afterwards after resetting my computer.

Now the battery won’t keep charge. It’s from 2017 so I don’t have any sort of warranty… what should I do?

Usually if RAM usage jumps like that while playing WoW, it's not the game itself but one or more of the addons being used. I would doublecheck your addons and make sure they are all up to date, and also remove any you are not using, especially if two or more of them duplicate functionality.