this post was submitted on 31 Oct 2024
446 points (92.9% liked)

linuxmemes

21304 readers
1096 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!

    Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't fork-bomb your computer.

    founded 1 year ago
    MODERATORS
    poopsmith@lemmy.world
    zephyr@lemmy.world
    rtxn@lemmy.world
    446
    Handling non-responsive and frozen applications (lemmy.ml)
    submitted 2 weeks ago by Kory@lemmy.ml to c/linuxmemes@lemmy.world
    46 comments fedilink hide all child comments
     

    Seen on the FOSS Weekly #24.44: https://itsfoss.com/newsletter/foss-weekly-24-44/

    you are viewing a single comment's thread
    view the rest of the comments
    [–] cypherpunks@lemmy.ml 4 points 2 weeks ago* (last edited 2 weeks ago) (1 children)

    The canonical documentation is https://www.kernel.org/doc/Documentation/filesystems/proc.rst (ctrl-f oom) but if you search a bit you'll find various guides that might be easier to digest.

    https://www.baeldung.com/linux/memory-overcommitment-oom-killer looks like an informative recent article on the subject, and reminds me that my knowledge is a bit outdated. (TIL about the choom(1) command which was added to util-linux in 2018 as an alternative to manipulating things in /proc directly...)

    https://dev.to/rrampage/surviving-the-linux-oom-killer-2ki9 from 2018 might also be worth reading.

    How to make your adjustments persist for a given desktop application is left as an exercise to the reader :)

    [–] QuazarOmega@lemy.lol 2 points 2 weeks ago

    Thanks! Will have to come back to this