-
Notifications
You must be signed in to change notification settings - Fork 157
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Notify-send slowdown #73
Comments
Earlyoom slowdowns until notify-send runs. Adding '&' fixes problem. |
I see. But we also have to stop sending notifications until the first one is finished. |
Otherwise we may spawn too many processes, and slow the system down even worse. |
Have you seen this in fact even once? |
Slowdown the system will stop after 1st SIGKILL. |
Yes i have seen this with cronjobs that pile up. The server then enters a death spiral |
Send the GUI notification AFTER killing a process. This makes it more likely that there is enough memory to spawn the notification helper. #73
earlyoom was sending the notification first, and kills later. As sending the notification needs memory, this was stupid. The change b2fe57c kills first, and notifies later. Does this fix the slowdown you see? |
I need test it, I try it later. |
PS: c91dc9e |
Thank you very much |
Works great, thanks! |
Thanks for testing! |
I ran even
and nothing happened. |
That contradicts what you saw in #73 (comment) , right? |
...if
&
not in the end of the command.Replace
"-i dialog-warning 'earlyoom' 'Killing process %d %s'", victim_pid, victim_name);
with
"-i dialog-warning 'earlyoom' 'Killing process %d %s' &", victim_pid, victim_name);
will fix the problem
The text was updated successfully, but these errors were encountered: