Thanks for mentioning that, I did not know there was now a tool to
take care of this job.
The default for earlyoom won't fix that issue if you have enough swap
space defined. it defaults to don't TERM until 50% of swap is left.
My machine is swapping on SSD and the machine is mosly useless once it
gets less than 1gbyte into swap.
I have added an option on one of my machines that has seen issues
often (only 10GB ram) to -s 95,95 so it will allow a little bit of
swap before killing.
I will refresh the web page I know will act up within a day or 2 and
see if it kills it fast enough.
On Wed, May 20, 2020 at 7:55 AM Ed Greshko <ed.greshko(a)greshko.com> wrote:
> On 2020-05-19 23:05, Roger Heflin wrote:
> > Keep in mind if it does not "crash" and you have enough swap that the
> > machine will just get so slow as to be useless.
> And that is exactly the type of problem earlyoom is trying to solve.
> Users should also be aware that, by default, earlyoom is called with
> Preferring to kill process names that match regex '^Web Content$'
> With "Web Content" being a firefox thing. Other web browsers are not
immune to eating up
> excessive memory due to number of tabs open and the content being served. So, if
> a firefox user and you'd rather earlyoom kill one of your tabs instead of picking
> application you may be running you'd need to adjust the setting.
> You also may wish to add to the --avoid list.
> The key to getting good answers is to ask good questions.
> users mailing list -- users(a)lists.fedoraproject.org
> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct:
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: