Database Search
If you can't find the information using the categories below, post a question over in our WinBatch Tech Support Forum.
TechHome
Process ID
- !!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.
Get Mem Usage of a Running script
Keywords:
DllHwnd Get Current Process ID PROCID Proc Id GetWindowThreadProcessId
Question:
I am interested in having my script to verify how much memory it is using. If the process is higher than 12mb restart itself. This should solve a strange memory leak problem I am having due to some problems with an API I am calling.I need memory usage of a process like I see in task manager!
Answer:
Apparently the "Mem Usage" you see in Task Manager is really the 'working set size' of the process. The working set is basically the set of physical memory pages that the process is using.Fisrt, you would need to get the ProcessID of the running script. Then you could use tGetProcInfo from the process extender to retrieve information about the memory usage of the process...
#DefineFunction GetProcessID(h)
bb=BinaryAlloc(4)
BinaryEODSet(bb,4)
dllname=strcat(DirWIndows(1),"user32.dll")
DllCall(dllname,long:"GetWindowThreadProcessId",long:h,lpbinary:bb)
p=BinaryPeek4(bb,0)
return (p)
#endFunction
;Addextender("wproc34i.dll")
Addextender("wwprc44i.dll")
hwnd=DllHwnd("") ; window title goes in here
procname = WinExeName("")
pid=GetProcessID(hwnd)
ret=tGetProcInfo(pid)
wss= itemextract(3,ret,@TAB)
kb_wss = wss/1024
message("Memory Usage on process %procname%",StrCat(kb_wss," KB"))
Article ID: W15859
File Created: 2013:04:01:09:09:04
Last Updated: 2013:04:01:09:09:04