This setting "Memory Breaker" is a function to forcibly avoid the problem of the system itself stopping responding if the memory exceeds 100% on a remote-controlled virtual PC, so it should not be used on a regular PC. Don't go.
This feature was introduced in 0b143.
When the physical memory usage rate reaches the specified percentage (specified between 50 and-100), the process using the most memory will be forcibly terminated.
In cases where remote-controlled Windows runs out of memory for remote desktop connections due to problems such as memory leaks, the purpose is to prevent the entire OS from stopping by stopping the enlarged process by dropping a breaker. Available for
There are probably only disadvantages to using this function on a Windows 10 local PC, so please be careful when using it.
The memory usage ranking of processes is selected based on the WorkingSet value of the process when the Top Processes system is on.
The breaker is not a cleaner that reduces consumption, but a forced limiter, so the target application will not be processed when it terminates normally. Please consider this disadvantage carefully before using it.
This forced termination is executed at the cycle of the top process, and the processes are terminated in descending order of usage until the usage falls below the specified percentage.
Avoid using it together with RAM drives that create virtual drives on memory, as it is extremely dangerous.
The following executable file names will be ignored (not subject to termination).
・"explorer", "csrss", "smss", "services", "svchost", "winlogon", "dwm", " thilmera7 ", " thilmera7s "
・Something running as a service.
・ thilmera could not obtain permission to terminate the process.