You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For me as casual user, is more conveniently to choose process which should be killed. It is difficult to constantly update the priorities of processes in the config, especially since various situations may arise that will be decided not in favor of the user.
I think it's better to show list of worst processes and possibility to pass SIGTERM, SIGKILL to one or many of them. If the indicator of the load on the subsystem reaches critical values, then the process is automatically killed, as it works now.
The text was updated successfully, but these errors were encountered:
For me as casual user, is more conveniently to choose process which should be killed. It is difficult to constantly update the priorities of processes in the config, especially since various situations may arise that will be decided not in favor of the user.
I think it's better to show list of worst processes and possibility to pass SIGTERM, SIGKILL to one or many of them. If the indicator of the load on the subsystem reaches critical values, then the process is automatically killed, as it works now.
The text was updated successfully, but these errors were encountered: