Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #247346

Re: Out of memory killer misconfigured?

From piorunz <piorunz@gmx.com>
Newsgroups linux.debian.user
Subject Re: Out of memory killer misconfigured?
Date 2022-04-18 22:10 +0200
Message-ID <EdFR7-9Dbo-1@gated-at.bofh.it> (permalink)
References (3 earlier) <E7iDU-5CdC-1@gated-at.bofh.it> <EciDf-8NOj-1@gated-at.bofh.it> <Ecn9T-8Qsj-1@gated-at.bofh.it> <Ecr3P-8T0A-9@gated-at.bofh.it> <Ecrdv-8T4E-7@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On 15/04/2022 11:14, tomas@tuxteam.de wrote:

Thanks for your reply, I appreciate your patience.

> - At the "low level": you are talking about "process trees".
>   Perhaps that's the problem. Perhaps, towards the OOM score,
>   all those processes count as individual processes.

Each 8GB individual process should be killed absolutely first, not
entire KDE desktop and Xorg. That's obvious.

> Note that
>   the OOM killer is just the last straw the system grabs to
>   try to avoid sinking. Perhaps it's the wrong instrument for
>   your case and you need to look into limits, or cgroup memory
>   policies.

I look from desktop perspective. OS (Linux) runs my desktop and manage
all programs. When one programs eats too much memory, program gets
killed. That is default behaviour or any mature operating system, even
in Windows 2000 era we had this. I don't understand why Linux, using all
its tools available to itself, is not handling this. I highlight tools
available to it, not to me - I should not need to know which internal
Linux tool kills misbehaving programs and how it works to use my desktop.

> - At the "higher level": "you see how things are broken" for
>   you. You are still (in my opinion) committing the error of
>   generalising your problem /before/ you have spent enough
>   time investigating it. That might make it more difficult
>   finding a satisfying solution :-)

Yes, I look absolutely from higher, desktop level. Current defaults are
broken. OOM is not working, and it's killing entire system instead of
one offending application. That's a bug.

> Plus, don't assume random
>   kernel programmers aren't smart. They usually are. And they
>   usually spend quite a bit of effort until a patch of this
>   kind goes in.

Of course they are very smart. However, in this case, and in hundreds of
similar cases which are being reported as bugs every year, defaults, or
other mechanisms, needs to be adjusted so Denial of Service is not
happening when application takes all memory. Right now, that is exactly
what's happening. System-wide DoS in one second, entire system nuked and
halted when one Wine application claims too much memory.

>
> Cheers


--
With kindest regards, Piotr.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄⠀⠀⠀⠀

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

Out of memory killer misconfigured? piorunz <piorunz@gmx.com> - 2022-03-29 11:40 +0200
  Re: Out of memory killer misconfigured? Sven Hoexter <sven@stormbind.net> - 2022-03-29 12:10 +0200
    Re: Out of memory killer misconfigured? piorunz <piorunz@gmx.com> - 2022-03-29 20:40 +0200
      Re: Out of memory killer misconfigured? Tixy <tixy@yxit.co.uk> - 2022-03-30 10:20 +0200
        Re: Out of memory killer misconfigured? piorunz <piorunz@gmx.com> - 2022-03-31 19:00 +0200
          Re: Out of memory killer misconfigured? Jonathan Dowland <jon+debian-user@dow.land> - 2022-04-20 12:30 +0200
            Re: Out of memory killer misconfigured? piorunz <piorunz@gmx.com> - 2022-04-20 17:30 +0200
              Re: Out of memory killer misconfigured? Jonathan Dowland <jon+debian-user@dow.land> - 2022-04-20 18:20 +0200
                Re: Out of memory killer misconfigured? piorunz <piorunz@gmx.com> - 2022-04-20 19:50 +0200
                Re: Out of memory killer misconfigured? David Wright <deblis@lionunicorn.co.uk> - 2022-04-20 20:40 +0200
    Re: Out of memory killer misconfigured? piorunz <piorunz@gmx.com> - 2022-03-29 20:50 +0200
      Re: Out of memory killer misconfigured? Greg Wooledge <greg@wooledge.org> - 2022-03-29 21:20 +0200
        Re: Out of memory killer misconfigured? piorunz <piorunz@gmx.com> - 2022-03-29 22:10 +0200
          Re: Out of memory killer misconfigured? Greg Wooledge <greg@wooledge.org> - 2022-03-29 22:20 +0200
    Re: Out of memory killer misconfigured? piorunz <piorunz@gmx.com> - 2022-03-29 21:00 +0200
      Re: Out of memory killer misconfigured? Nicholas Geovanis <nickgeovanis@gmail.com> - 2022-03-29 21:20 +0200
      Re: Out of memory killer misconfigured? <tomas@tuxteam.de> - 2022-04-01 08:10 +0200
        Re: Out of memory killer misconfigured? piorunz <piorunz@gmx.com> - 2022-04-15 03:10 +0200
          Re: Out of memory killer misconfigured? <tomas@tuxteam.de> - 2022-04-15 08:00 +0200
            Re: Out of memory killer misconfigured? piorunz <piorunz@gmx.com> - 2022-04-15 12:10 +0200
              Re: Out of memory killer misconfigured? <tomas@tuxteam.de> - 2022-04-15 12:20 +0200
                Re: Out of memory killer misconfigured? piorunz <piorunz@gmx.com> - 2022-04-18 22:10 +0200
                Re: Out of memory killer misconfigured? Tim Woodall <debianuser@woodall.me.uk> - 2022-04-19 17:50 +0200
                Re: Out of memory killer misconfigured? <tomas@tuxteam.de> - 2022-04-19 18:10 +0200
                Re: Out of memory killer misconfigured? Nicholas Geovanis <nickgeovanis@gmail.com> - 2022-04-19 22:10 +0200
  Re: Out of memory killer misconfigured? Jonathan Dowland <jon+debian-user@dow.land> - 2022-04-20 12:30 +0200

csiph-web