search

lowleveldesign / process-governor

This application allows you to put various limits on Windows processes.
MIT License
626 stars 62 forks source link

"System cannot find the file specified" for Teams.exe #54

Closed anthonyg2003 closed 1 year ago

anthonyg2003 commented 1 year ago

A single instance of Teams seems to run around 10 teams.exe processes, and so to keep it under control, I tried using the maxjobmem option:

procgov64 -r --maxjobmem 200M -- teams.exe

which returned: image

Does the process executable file need to be in the PATH? I tried using the file path in the command line and that returned a parsing error.

Using a single PID instead of teams.exe works in that it executes eventually - although takes sometimes minutes and the process just seems to end, but trying multiple PIDs fails with a "ERROR: Not enough quota available to process this command." But even if that worked, not sure that would result in what I want since I ultimately want to restrict all the teams.exe processes and teams just seems to spawn new ones.

image

lowleveldesign commented 1 year ago

If teams.exe is not in the PATH then you need to provide the full path to the executable, for example:

procgov64 -r -m 700M C:\Users\{username}\AppData\Local\Microsoft\Teams\current\Teams.exe

Regarding the quota issue and problems with Teams, procgov won't fix the application. Unfortunately, Teams require a lot of memory and when you set the limit too low you will either break the application or make it too slow. I'm not sure what's your scenario, but maybe you should rather look at options to limit the physical memory (--minws, --maxws) or total job memory (--maxjobmem)