this post was submitted on 09 Feb 2024
127 points (95.7% liked)

linuxmemes

21251 readers
1580 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
    [email protected]
    [email protected]
    [email protected]
    127
    crash in Ubuntu GNU/Linux (discuss.tchncs.de)
    submitted 9 months ago by [email protected] to c/[email protected]
    56 comments fedilink hide all child comments
     

    this is the first time in many years of my GNU/Linux journey that I saw a BSOD. on my office machine BTW. personal machine has never crashed even once.
    the crash was due to 100% RAM and swap usage.

    image description:
    a mobile-clicked photo of a laptop screen. the background is full black with a sad computer image in the middle. the text below it reads: "Oh no! something has gone wrong. A problem has occurred and the system can't recover. Please log out and try again."
    just below it is a small button with the text "log out"

    you are viewing a single comment's thread
    view the rest of the comments
    [–] [email protected] 5 points 9 months ago* (last edited 9 months ago) (2 children)

    Carelessly running too many programs and not having much RAM.

    When I get my Framework 16, I'll either get 64 or 128GBs of RAM. It's so cheap nowadays, the only thing stopping me from getting more is simply the increased time to go to sleep and wake up.

    [–] [email protected] 6 points 9 months ago* (last edited 9 months ago) (1 children)

    Tends to be mem leak in bad code for me

    [–] [email protected] 5 points 9 months ago (1 children)

    Yeah i only get near 100% when I'm doing a lot of virtualization or running nyx for a long time since there's a memory leak in there.

    [–] [email protected] 0 points 9 months ago (1 children)

    Wouldn't of thought nyx would be unstable.

    [–] [email protected] 2 points 9 months ago

    Not unstable nor unreliable, just a bit buggy. Every so often you gotta do a quick qq to exit and wait up to 5 minutes for it to let go of the ram. On occasion I've had to terminate the process as it was doing something wacky.

    [–] [email protected] 2 points 9 months ago

    I have 16 GB and it feels like a lot. I run virtual machines and I still have leftovers