Anton Aylward wrote:
On 12/01/2020 11:51, Per Jessen wrote:
jdd@dodin.org wrote:
Le 12/01/2020 à 17:15, Anton Aylward a écrit : (...)
that is what the 'working set' is all about.
interesting, but not the question I try to understand
somebody said "when memory leaks, the system crashes".
is this true (*crash*)?
When the system starts to run out of memoru, the OOM killer will kick in and try to identify who is gobbling up the memory. If it pick an innocent process, it could be seen as the system crashing.
That is possible with the default setting, yes.
However you can also configure it so the OOM_killer targets the process that caused the OOM condition and only that.
Care to share an example? In my experience, the oom killer kills the _best_ process, which is the one that uses the most memory. There is way of influencing the choice, I'm not sure how. I had a situation over Christmas where a customer's webserver essentially died (I may have mentioned this situation before) due to trying to serve too many requests. Loads of apache threads gobbled up the memory and the OOM killer decided to get rid of mysql. (an innocent, but important victim). -- Per Jessen, Zürich (2.9°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org