• rotopenguin@infosec.pub
    link
    fedilink
    English
    arrow-up
    3
    ·
    15 days ago

    The OOM killer always, invariably starts off with killing the display server. Any side effects such as “the notification daemon loses its connection and closes” or “every single thing that you were working on loses its connection and closes” is incidental.

    • Swedneck@discuss.tchncs.de
      link
      fedilink
      arrow-up
      1
      ·
      14 days ago

      i will never stop wanting to commit severe crime every time i try to see what’s using the processor and every single fucking system monitor tool just says it’s xorg

      YES THANK YOU VERY USEFUL GOOD

      • rotopenguin@infosec.pub
        link
        fedilink
        English
        arrow-up
        2
        ·
        14 days ago

        At least Windows has more precise monitoring, it will tell you whether the process is “Windows Telemetry” or “SVCHOST.EXE”.