The leak’s 1.5GB/hr rate is probably proportionally based upon a one craft per 1.8 second speed. I wouldn’t be surprised if it’s occurring faster alongside faster crafting speed.
I see a forum mod moved this over to bug reports. I already have an open bug report:
Considering that languages that run on top of frameworks today they do have their own garbage collector, wow is a C++ application and therefore needs its own garbage collection routine being called and memory released.
Either something blocks the garbage collector at that window or they forgot to call it lol.
Yes indeed sir. I’m not talking about just games though so that’s my fault for not emphasizing “any” class of app.
There’s a clinical app that , while the vendor is still trying to address it, it leaks about 2gb per hour. And that’s without doing anything…it’s an app that analyses data captured from other systems then it creates reports based on the providers specific needs. Even when it’s just open and not capturing its leaks. It’s a joke among our dept. a punchline for bad coding if you will. Thankfully it’s the vendors problem not ours to solve.