Can't find the information you are looking for here? Then leave a message over on our WinBatch Tech Support Forum.
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.
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.
Article ID: W15863
File Created: 2017:07:28:12:58:39
Last Updated: 2004:03:30:14:41:12