

Screen Resolution: 1920 x 1080 x 60 hertz Monitor(s) Displays: Samsung 27" Curved C27F591 Sound Card: Realtek High Definition Audio Graphics Card: NVIDIA GeForce GTX 3080 w/10GB GDDR5X mem OS: Multi-boot Windows 10/11 - RTM, RP, Beta, and InsiderĬPU: 11th Gen Intel(R) Core(TM) i9-11900KF 3.50GHz, 3401 Mhz, 8 Core(s), 16 Logical Processors System Manufacturer/Model Number: Alienware R12 So now that this has been explained do you experience this? Do you think it's Firefox or a recent system update? Either the system or an app is munching up RAM out of normal parameters. If that is not the right term for this I kinda don't care because that's the experience of it. So much faster I call it a 'memory leak'.

Until recently when it expands seemingly much faster. I find that it usually takes about 4 or so hours for that blue line to eat up the remaining free RAM. And the issue goes right away with a reboot. How do I know this? Whenever typing goes to a crawl I open resource monitor and, sure enough, that blue 'standby' RAM has filled everything up. Typing in Firefox suddenly goes to a crawl. Perhaps it is but I can assure you of this - once that blue line grows to take up the remaining available 'free' RAM. That it's 'reserved' to help my open apps run better. See that blue line of 'standby' RAM? I know there are people who will swear up and down and left and right that standby RAM isn't really used RAM at all. If I do a fresh boot and open Firefox with a handful of tabs, I get this from Task Manager -īut if I open Resource Monitor I see this. In Windows 10 I know of two places I can check RAM usage. So I have to first explain my perspective on RAM before I can even talk about a 'memory leak' or what might be called 'RAM hogging'. Tasks: 311 total, 1 running, 310 sleeping, 0 stopped, 0 zombie I did not find an answer in the similar questions I did consult (most of them several years old)

I tried to troubleshoot with the logfile but it seems to be empty.

The memory usage of xorg as a child process of sddm keeps growing with time.Įverytime I restart my computer, the problem reappears after a few dozens of minutes.
