Quote:
We've been taking a lot of snapshots of memory allocations and comparing this data to the code from different times. We've gone back as far as June, rebuilt the code and compared these allocations to today's code. We have an understanding of what is happening and when. Unfortunately it's not as simple as rolling the code back to June because it would take a lot of other code with it. So we're working on a way to fix the problem correctly.
There are actually two issues coming into play. There appears to be an issue with data not being cleared from the cache as aggressively as it should. This isn't really a memory leak, its just the client holdng on to things that it can probably get rid of, especially after zoning. Then there is also the issue of memory becoming fragmented which eventually causes the allocation error. Both should really be fixed if possible, but as soon as we have a fix for one or the other, we will get it out asap. Fixing either issue should keep the client from crashing as much as it is.
I'll let you know when I have more info.
There are actually two issues coming into play. There appears to be an issue with data not being cleared from the cache as aggressively as it should. This isn't really a memory leak, its just the client holdng on to things that it can probably get rid of, especially after zoning. Then there is also the issue of memory becoming fragmented which eventually causes the allocation error. Both should really be fixed if possible, but as soon as we have a fix for one or the other, we will get it out asap. Fixing either issue should keep the client from crashing as much as it is.
I'll let you know when I have more info.
Edited, Oct 18th 2009 3:05pm by Calthine
