home.social

#oomkiller — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #oomkiller, aggregated by home.social.

  1. AI "Killed" by the Linux OOM-Killer? 🛑 Stop the silent assassination.

    The 2-min protocol to fix AI crashes:
    ✅ Strict Mode: vm.overcommit_memory = 2
    ✅ Full Alloc: vm.overcommit_ratio = 100
    ✅ Docker Shield: --oom-kill-disable

    Stop Cloud "Memory Ballooning." Get 100% Dedicated RAM on #ServerMO Bare Metal. 🏢⚡

    Read the full protocol:
    🔗 servermo.com/howto/stop-linux-

    #AI #Linux #PyTorch #DevOps #BareMetal #SysAdmin #MachineLearning #OOMKiller #SelfHosted

  2. #HomeAssistant with #ZHA in #Podman just crashed hard.

    The #ConBee 2 stick restarted (probably due to Frigate #FFmpeg #OOMKiller), thus the ttyACM-path changed.
    But that didn't exist anymore.
    So ZHA stopped running.

    Didn't get this to work reliably without --privileged … so HA now runs in a privileged Podman container with passed through /dev.

    #Linux #AppArmor #Debian

  3. Sentry noticed an issue with my app that Apple's crash reporting did not. The app used way too much memory in one view and got killed by iOS. Sentry gave me all the info I needed to find out what had happened and fix it. I had some real dumb stuff in a view containing a list where each item was pretty heavy. No issues as long as the number of items was low, but quickly got into huge numbers with more items. So, very happy with what Sentry can do.

    #ios #oomkiller #sentry #saved #my #bacon

  4. There's a joke that software dev is like solving a crime, and you're the murderer.
    And yet, here I am trying to figure out why PHP was murdered by "The OOM Killer"

  5. @fribbledom

    🍬 #OOMkiller isn't hard enough on #Firefox. Also, since when has Firefox used significantly more RAM than Chromium? 🍬