Quote:
|
Originally Posted by Andreas Raht
Markus & jarmenia, sorry but you're wrong  A leak is if the program allocates memory and doesn't free it *when it's no longer needed*.
What we have here, is a cache. Templates and text file content and also other stuff is being cached. When the cache is full or when you close the game, the cache will be written into a file and then the used memory will be freed again as it should be (so it's no leak). When you start the game again, the cache will be empty, so the game will use less RAM. After simulating some games it will be used again and it will need RAM again.
So Marc is right, it's just the cache.
I've tested it several times for memory leaks, and there are no leaks in the game at the moment  |
If the program is written to continue to take memory until the system drags to a hault, then yes, its not a memory leak just a memory hog. The result is the same however as system performance degrades over time. The program should run the same in the first 15 min as it does five hours later. This is not the case and I'll be happy to send you the performance logs when I get home if you want to see them.
Perhaps a solution to this is to empty the cache every so often, say once a year or every so many games. I'm not sure what exactly your caching or why so I can't propose a solution. The one thing I can say though is it needs to be looked at and I'll do whatever you ask to help resolve it. The way it is right now I can't run a 100 year sim without restarting the game every 20 years or so.