When do we have a problem with virtual memory using Fastmm4?

Question

We have an application whose virtual memory is growing and continues to work throughout the day. Two days later, it rose to 500 MB. I tried to profile applications that fall into the database, and also makes a lot of requests for HTTP and soap, but Fastmm4 shows that there are no leaks.

I'm not sure how and when the memory is declared, and if there is a problem with growing virtual memory?

Jd

Answer 1

it may not be a “memory leak”, but a more “accumulation” of it. The memory does not leak until the application can free it. for example, after the pointer is lost.

, , ( , ). - ( ). , , , / ( ). , , , , FastMM , ( , )

, , Objects ( AQ Time, ). /2 /3 . (, ) () , . , , , , , . , .

, - , , , . , , .

Answer 2

: -? .

Answer 3

-, , , . , AQTime.

Answer 4

, : . FastMM4, .

- - heapmanager (getheapstatus) , FreeBig FreeSmall . , - heapfragmentation.

Totalallocated , . , , .

, , , tstringlist.

totalallocated , .

Answer 5

Win2008.

If you accidentally use MDAC (ADO) on a Windows 2008 (or Win7) server and make many connections, there is a leak in the MS code, which clears the Connection Information .

From MS: "A leak occurs in some kind of security code that is used to remove things such as passwords from connection strings. Perhaps this is due to the fact that the following may be indicated in the connection string:" Persist Security Info = true ""