• 26 Posts
  • 1.84K Comments
Joined 3 years ago
cake
Cake day: July 7th, 2023

help-circle








    1. Get some sort of resource monitor running on the machine to collect timeseries data about your procs, preferably sent to another machine. Prometheus is simple enough, but SigNoz and Outrace are like DataDog alternatives if you want to go there.
    2. Identify what’s running out of control. Check CPU and Memory (most likely a memory leak)
    3. Check logs to see if something is obviously wrong
    4. Look and see if there is an update for whatever the proc is that addresses this issue
    5. If it’s a systems process, set proper limits

    In general, it’s not an out of control CPU that’s going to halt your machine, it’s memory loss. If you have an out of control process taking too much memory, it should get OOMkilled by the kernel, but if you don’t have proper swap configured, and not enough memory, it may not have time to successfully prevent the machine from running out of memory and halting.











  • Not sure what the Frame means with any of this. It’s going to be running the same stack as Deck, which is KDE. It’s also not going to be any sort of headset for your PC, at least at the outset.

    As for your other Dr questions, it’s all just personal preference. The Desktop is just window dressing on a compositor and window manager anymore. If you’re comfortable without all the system helpers and convenience of using either Gnome or KDE, you can just run a WM like Hyprland or Sway instead.