tsk, on 30 October 2012 - 06:44 AM, said:
That never worked for me.
I still think some sort of memory leak is occurring as memory usage grows at least 100mb for every map I play.
This isn't necessarily a memory leak. It may be, just not
necessarily.
You've all heard of the shader cache. The point of a cache is to...cache things--take things that are loaded frequently and put them somewhere easy (or easier) to read than wherever they're stored in the game install. When you play on a map it's going to load any textures, shaders, or whatever else particular to that map into the cache to try to speed things up next time around.
The thing to remember is that it will periodically dump assets from cache that haven't been needed for a long time, but managing a cache is basically voodoo. A tremendous amount of math and fiddling goes into figuring out what things can be dumped from cache when. Maybe it needs to be more aggressive in clearing out cache or maybe it doesn't. It's not something you can really tell by looking at task manager.
Now, if memory usage increases without bounds then yeah that's obviously a leak. Problem is it may well be one of those spooky "it leaks memory when the moon is full and the player is naked." As I said, cache invalidation is voodo. I've heard it said that it's one of only two truly hard problems in computer science (the other: naming things). Best thing you can do is post specs so the devs know about it. This is one of those things that's legitimately very hard to track down, especially for a small team.
TL;DR: the fact that memory usage grows after a match doesn't necessarily indicate a memory leak.
Sidenote: if you're posting about seeing anomalous memory usage it's a really good idea to specify approximately how much we're talking about. The devs probably have a better idea how much the game is really intended to use in the worst case than we do. Also, some people are a little behind the times on such things, like all the folks who open task manager in Windows 7 or Vista while idling, see very little free memory, and say Windows is bloated and inefficient, not realizing that a huge part of that usage is cached executables, DLLs, etc that can all be dumped effectively instantly if memory is needed.
Edited by Blue Footed Booby, 15 October 2013 - 08:49 AM.