Database Search
TechHome
- !!NEWSFLASH!!
- 213 Cannot Retrieve Counter Index
- 215 tListProc Failed
- 228 tGetData Failed
- Check if a Process is using CPU
- Check if a Remote Process is Running
- Close All Instances of an Application
- Enumerating Process Objects
- Error 207 (SunMonTueWedThuFriSat)
- Get CPU Usage
- Get Mem Usage of a Running script
- Get process id from process name
- Get Process Times UDF
- Get Sub Process Names From NTVDM
- Get Username from a Process
- How to Access Perfmon Counters
- List of Errors
- Memory Leak Using tGetdat on Web Service Counter
- Obtain Window Ids From a Process Id
- Physical Memory on Remote Machine
- Process Extender memory leak
- Process Id to Window Id
- Process Names Are Truncated tListProc
- Process Object Names Are Truncated in Performance Monitor
- Remote Process List
- Status of Process on Remote Machine
- tCloseProc( ) to Close a Program
- tGetData error 224
- tGetData returns same results
- tGetLastError vs WIL LastError
- Ticker Sample Code
- tListProc 213 Cannot Retrieve Counter Index
- tOpenProc Error 220 When Trying toTerminate a Process
- tRemoteConn Eating Up Memory
- tRemoteConn Issue
Can't find the information you are looking for here? Then leave a message over on our WinBatch Tech Support Forum.
Process Extender memory leak
Question:
I have written a simple "watchdog"-app that monitors a couple of computers (15) to se if a specific process is up and running.The app writes the info to a file with a time stamp and a error code that looks like this:
0 = OK 1 = Process does not exist 2 = Can't connect against the computer 3 = Doesn't respond to PING
Then the app. waits for a specified amount of time and then does the whole thing all over again. I'm using both the WinInet-extender and the process-extender to help me out. But after a couple of days my memory tends to be all used up. My own humble feeling is that the tRemoteConn function should have a matching disconnect-function. But thats just a guess from my side of the Atlantic.
My compiled app has acquired approximately 120mb of memory after 3 days of nonstop execution. That’s why I was lead to believe that my new app was the one to be blamed for my lack of memory ;o)
So...Memory, leak or bad code? Please some help.
Answer:
While awaiting a possible determination of the problem, one trick is to have the the program execute itself and exit every few hours or 1000 loops or something. This usually has the effect of dropping the built-up baggage and starting afresh.MORE....
What windows platform are you running on?
Here are some known issues on various Windows platforms:
Note: Some of the functions in the Process extender access the PDH APIs.
http://support.microsoft.com/default.aspx?scid=kb;en-us;263221
http://support.microsoft.com/default.aspx?scid=kb;en-us;306286
Article ID: W15863
File Created: 2004:03:30:15:41:12
Last Updated: 2004:03:30:15:41:12