this post was submitted on 12 May 2024
937 points (99.0% liked)

linuxmemes

20993 readers
1481 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
  • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.

  • Please report posts and comments that break these rules!

    founded 1 year ago
    MODERATORS
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] [email protected] 23 points 5 months ago

    No, the equivalent would be a kernel panic that the other user had linked. This is a situation where the RAM is fully used and a program's request for memory cannot be fulfilled. This is still a very bad situation because pretty much everything will grind to a halt. The Linux kernel thus makes a decision to kill a process (or multiple) until enough RAM is available again. Usually it kills the process with the most used RAM, but there's methods to influence the decision.