Jerky
18-08-2006 01:59:19
The problem started with our map editor getting SUPER slow. We thought it was a recent update, so after we checked out the commits on that day, there was no sign of the problem. I checked into it, and our app was doubling its memory footprint each time is loaded. Since many of us experienced this around the same time, we thought it was some recent updates of ours, but that turned out to be a crazy coincidence (like 4 of us all on the same day).
It turned out that our terrainname.info.cfg file was 120MB. (I found out after trying to open it in notepad, boy was that a mistake ). At that point, it takes the app over 3 minutes to load. After purging the file, our app began running perfectly again, but I decided to keep my eye on it. I searched to find out what the file was, since it seems to be a recent addition to our PLSM app. On first load, it starts at 15kb. The next load it goes to 30, then 60, then 120, 240, 480, 1mb, 2mb, and on and on and on. The growth is exponential (obviously).
Is that normal? Is there a way to have it delete itself after we exit the app, and do we want to do that? I read here that it is a cache, but what is it caching and do we need it?
Thanks in advance.
It turned out that our terrainname.info.cfg file was 120MB. (I found out after trying to open it in notepad, boy was that a mistake ). At that point, it takes the app over 3 minutes to load. After purging the file, our app began running perfectly again, but I decided to keep my eye on it. I searched to find out what the file was, since it seems to be a recent addition to our PLSM app. On first load, it starts at 15kb. The next load it goes to 30, then 60, then 120, 240, 480, 1mb, 2mb, and on and on and on. The growth is exponential (obviously).
Is that normal? Is there a way to have it delete itself after we exit the app, and do we want to do that? I read here that it is a cache, but what is it caching and do we need it?
Thanks in advance.