Quote:
|
Originally Posted by rdomico
I might be wrong, but I don't think it is a memory leak. Close the game down, reboot and then reload your game. You will see that the memory usage will be about the same.
I think it is a design decision. I can't see the code, so I can only guess, but it appears as though the game keeps the entire database(or a lot of it) in memory. The pro of that approach is faster access. Reading/Writing to a file is slow. Reading/Writing to memory is fast. The con is just what you are seeing.... a lot of memory.
|
No that would not be a design decisision, it would be a memory leak. If the game continues to take more and more memory without releasing it up to the point where a strong system will grind to a halt, that my friend is a memory leak. When I restart the game, the memory doesn't imediatly jump back up to 1 + gigs so its not loading the whole database at once. The reason the memory returns to the system once the game is closed is the fact that windows XP does its job and when OOTP is closed, XP releases any memory allocated to it that was not released by the application its self.
Besides, think about it. Most people don't have 2 gigs of ram in their machine. If it brings my machine to a halt, what would it do to somone with 512 megs of ram?