Shoushin wrote:
Do i get it right ? All you guys are doing is just doing some hotfixes, workaround ? performance tweaks ? For heaven's sake. no matter how much improvement you are going to put in until you have the memory leak fixed this issue will always be around. Play for an hour or two, open LoN and you are crashing right away. Why cant you simply acknoweledge that there is a memory leak problem and try to actually dig down on the problem and fix it ? :/ That would be a hell bigger win in the long run especially with the next expansion incoming.
I am really disappointed by the attitude you guys are taking toward this. performance tweaks against a memory leak which would only postpone the crash. BAH.
PS: for real, if you keep doing this stuff, when the next GU comes out we're going to go down on the same path, memory consumption spikes, ppl crash, you do another set of hotfixes (which will again take a few months), then on the next GU rinse and repeat. After a while ppl will be bored of this.
This error has nothing to do with a memory leak which is why we won't acknowledge something that doesn't exist. We have memory leak detection code in the client and can tell instantly when the client shuts down if every piece of memory that was allocated has been deallocated. This is not the problem. People like to use the term memory leak because they can see the symptoms of a certain type of behavior and assume that's what the problem is.
Our "attitude" is to put as many resources as we can spare on this problem and do everything we can to fix it as quickly as possible. Optimizing memory is one way to do this and as you can tell from the responses, its helping a lot of people.
LINK
(Rothgar) Re:Re:Re:EverqQuest2.exe 1.8gigs of memory usage?!?!?
