Nooe. The reason it’s leaked is because the memory isn’t taken care of by the program. If you write program in a language that doesn’t have built-in garbage collection, like C++, and you don’t free all of your memory, your program leaks me.ory.
Dude you have made my day. I can just go lay down now and feel peaceful fulfillment.
This comment…
Does not in any way equate remotely to this comment:
Sorry you can’t seem to understand that. Have a nice day.
1 Like
This was the moment where your brain malfunctioned and we all had to suffer the consequences on your behalf.
It does break, quite regularly in fact.
Read above, genius. I’m not the problem here. Goodbye.
1 Like
IIRC the issue started week 2 of the expansion after a weekly update at the same time there were a lot or performance complaints. No idea what the garbage collection or memory allocating looks like for add on development but they’re still running in the games sandbox. So addons could be an aggravating cause but probably not the root.
If it was addons causing this it would probably be a much more prevalent and ongoing issue. Not suddenly pop up and go away.
Hey there genius, if Blizz makes decisions about WQs based off of what “evreyone said here”, then how is that not Blizz designing the game according to forums?
It’s annoying when someone is being pedantic, but it’s another thing entirely when that person isn’t even good at being pedantic.
*palm-face-head-desk-desk-desk-desk
Go back to school, take your meds, do something. Be better…
Memory leaks happen when unneeded storage isn’t properly discarded.
This is all discarded when the program ceases to run, or if it has a dump.
1 Like
What are you crafting lol ~~ but yes for science!
Not to beat you to death over this, but from the Computer Science perspective, OP has made a good observation. The goal of a CS academic in the realm of coding is to make that code as efficient as possible. Allowing for a memory leak that builds so significantly over time is heavily frowned upon.
I had a college professor who was a real stickler for this, and would 100% throw the book at students who allowed obvious memory leaks.
While your question is innocent enough, it is easy to interpret it as otherwise in this day and age.
2 Likes
We’d have Mer-Goblins (or Murlocs) as a playable race if that were to ever happen.
(Personally, I am all for it.)
1 Like
Vanguard: Saga of Heroes did it best
food… just kicking back and crafting on like 2 toons in booty bay while doing other things in between every 5 minutes I have to put down a new fire and cancel scan/relist.
It’s one of the few professions that weren’t nerfed in DF.
The fact I’m using two toons also let me confirm the leak scales linear with time. Both wound up with identically forever increasing RAM usage at the exact same pace at 1.5GB per hour.
1 Like
The operating system will release memory allocated by the program when the process exits.
Have you tried disabling all add-ons? Sounds like an addon has a leak
I have 64GB ram I say why the hell not
2 Likes
I have been having random and weird other problems with addons that do seem to come and go.
It IS being caused by blizzard. A few add-on devs’ when I searched for solutions have complained that blizz changed something in how the API/addons work. Lots of bugs in the addons themselves. But WoW without addons seems “fine”.
they come and go. most add ons these days seem to need nearly daily updates because of the bugs they’re encountering dealing with wahtever blizzard changed.
One of the most frustrating for me is how items in your bag work. It’s completely broken consoleport and most items cannot be used in your bag without errors and having to turn off addons everytime.
So ya, it’s likely something blizzard has changed in the WoW code. But it’s manifesting through addon use most likely.
If you rage craft for 2 days straight you’d be running out of RAM still, even with 64GB.
1.5 GB/hour leak goes brrr.
Reminder that this is still happening in 10.0.5.