KDE Will Nicely Notify You When Apps Are Being Killed Due To Out-Of-Memory

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • moonwalker
    Senior Member
    • Dec 2013
    • 172

    #91
    Originally posted by MrCooper View Post
    And brace for a bad time. Linux user space code generally either assumes that malloc never fails, or if there are error handling paths, they tend to be not well-tested. Long story short, malloc returning NULL is likely to result in fireworks.
    I believe I did imply as much.

    Comment

    • mrg666
      Senior Member
      • Mar 2023
      • 1034

      #92
      I just did another check on Plasma RAM usage on my laptop. It is Latitude 7400 with 16 GB RAM and Intel integrated GPU. The first is from text console (CTRL-ALT-F2) without Plasma session. Second is after logging into Plasma session using Konsole. Command is "free -h". Plasma version 6.2.2, QT 6.8 running in FC41. Plasma is using just 300MB.

      No Plasma
      Code:
                     total        used        free      shared  buff/cache   available
      Mem:            15Gi       1.3Gi        10Gi       223Mi       4.2Gi        14Gi
      Swap:          8.0Gi          0B       8.0Gi

      Plasma running
      Code:
                     total        used        free      shared  buff/cache   available
      Mem:            15Gi       1.6Gi        10Gi       199Mi       4.2Gi        13Gi
      Swap:          8.0Gi          0B       8.0Gi

      Comment

      • Rovano
        Senior Member
        • Jul 2014
        • 355

        #93
        A few months ago, I was at a machine about 13 years old with AMD 4cores. The machine has 2GB DDR2 RAM. I ran KDE6 there for a test. It ran beautifully smoothly.

        Avis could still rely on the GPU memory consumed.​

        Comment

        • WileEPyote
          Senior Member
          • Nov 2023
          • 211

          #94
          Originally posted by MrCooper View Post
          This might be self-inflicted pain.

          Without swap, the kernel can't reclaim anonymous data pages, so they all use up system RAM, even effectively unused ones. The only way the kernel can reclaim memory is by evicting file-backed pages, a lot of which are from executable binaries. As memory pressure increases, the kernel spends increasingly more time faulting back in pages to execute.
          Orrrrrrr, hear me out. Install an ungodly amount of ram and never worry about OOM or swap again.

          Comment

          Working...
          X