The page file leak is a small leak that has been in cs fire monitor for a long time, it takes days for it to grow that big. (By closing cs fire mon it goes away then reopen it) And I for the life of me haven't been able to trace it down. I have tried every tool I could think of to find out which API is causing it. I assume it is an API that's causing it cause if the main exe leaked it wouldn't grow in the page file the memory of the exe itself would. So one of the dll's that is used with an API is causing it.
There are over 20,000 lines of code in the program, and the leak is so slow it takes a day or to to see any build up, so trying to fix it is very hard and time consuming. I tried for a week, change a section, run the program, wait a day or so try another section, ugh! If could just find a way to pinpoint the leak.
Any help I can get trying to trace it down would be great and I would fix it in no time.
CS Fire monitor is a old program I made almost over 4 years ago. I think it is time when I get caught up to rebuild it.
-Shane
