noodles1
Programmer
- Oct 31, 2001
- 58
The Pervasive client programs that I am building at the moment seem to exhibit a strange behaviour. They appear to consume memory when run iteratively.
For example, I have a simple test program that opens a single database file and then closes it followed by a Stop operation. When I set it up to do this a repeated number of times, I can see through the use of either Windows Task manager (Peak Mem Usage) or Performance Monitor using Private Bytes of the Process object, that these values steadily increase over time.
I have confirmed that all mallocs etc. are correspondingly free'd throught the use of the C Run Time Heap Debug routines. I have isolated that memory consumption seems to be related to Pervasive operations.
I was expecting that all resources allocated upon the open call would be released when the Stop operation is issued.
Anyone else experince similar behaviour or point me in the direction of what to investigate.
These are Win32 programs.
For example, I have a simple test program that opens a single database file and then closes it followed by a Stop operation. When I set it up to do this a repeated number of times, I can see through the use of either Windows Task manager (Peak Mem Usage) or Performance Monitor using Private Bytes of the Process object, that these values steadily increase over time.
I have confirmed that all mallocs etc. are correspondingly free'd throught the use of the C Run Time Heap Debug routines. I have isolated that memory consumption seems to be related to Pervasive operations.
I was expecting that all resources allocated upon the open call would be released when the Stop operation is issued.
Anyone else experince similar behaviour or point me in the direction of what to investigate.
These are Win32 programs.