Hi,
Running openSUSE Tumbleweed KDE 64Bit fully updated.
I’m noticing a memory leak, RAM fills up after about 1 day of continuous use?
Running the following software:
Anyone have any ideas?
Desktop has 16GB RAM.
Below image URL link is of KDE System Monitor.
Thanks!
Jesse
Do not seem to have that much memory usage I see only 2-3Gig???
Completely normal.
There is no issue
I’m running TW and it’s all good
I concur with the comments made, it’s normal
Hi,
It’s “normal”??
The 16GB of RAM fills up every night I am sleeping
and I wake up to a KDE Plasma desktop that has crashed.
That’s not “normal”
Jesse
There is no mention of a crashing desktop in the title of this thread, nor in your first post.
Nevertheless people should have detected that crash? Is that normal?
That’s not normal. No crashes here. Memory fills up. I definitely want to use it. This is intended behavior:
**erlangen:~ #** free -h
total used free shared buff/cache available
Mem: 31Gi 10Gi 3.1Gi 932Mi 17Gi 19Gi
Swap: 0B 0B 0B
**erlangen:~ #**
What is actually in use and what is in the buffer?
Yes,
Woke up today and the system was frozen with all RAM used again…
Anyone have any ideas?
(this is a mission critical computer)
Jesse
You should really explain much, much more if you want adequate help.
Now it isn’t crashed, but frozen. And how can you check if the memory is full when the system is frozen?
I use a KDE panel widget which shows memory usage.
Woke up today and it displayed full and the computer was frozen.
Like I said in the original post:
Running the following software:
What information specifically do you need to troubleshoot this memory leak?
I know nothing about how Linux works so don’t know what to show here…
Actually,
This “memory leak” you describe may be normal behavior with all modern OS.
All modern OS nowadays is of the philosophy that unused RAM is wasted RAM, so if your system is busy it will naturally use more of your RAM all the time.
If you are continuously at your keyboard, when your system reaches the maximum available, it will discard data that’s not likely going to be used again to make it available for new tasks, but if you’ve been sleeping all night, your system might have been gradually filling up with no indication that you intend to run new tasks until you start typing… And then depending on what you are doing may have some difficulties estimating how much RAM needs to be freed up for your new tasks so might pause for a while.
There are ways to identify unintentional and actual memory leaks, they’re usually associated with programs you’re running.
If you’re sleeping while your machine is at work at night for long periods of time, verify you’re not experiencing pauses or freezing during the day or your normal activities. If the problem is too onerous in the morning, try “waking up” your machine by scheduling something to happen before you sit at your keyboard.
TSU
Hi
Did you not read what the user is indicating?
The machine is left on overnight, for example, when I leave my desktop at night I am using for example 3GB of RAM, when I come back to it in the morning I’m using 3GB of RAM. The OP is for example using 3GB of RAM, when they come back in the morning it is using 16GB of RAM and unresponsive. Ergo NOT NORMAL Behavior, a memory leak for sure in what ever applications are running…
When you’re ready to goto bed each night, shut down a different one of the big apps first. Repeat each day until the leak is absent when you get back to work. I’d start with LOC or VNC Viewer. I don’t imagine you’re doing much calculating or viewing while asleep.
It might be worth us considering if your TW install is being managed correctly.
Have you added repos?
zypper lr -d
I have TW KDE and it’s rock solid.
Lots of suggestions here. I will add one.
Are you having these same applications active during the day? Then check e.g. every hour how much memory each one uses. You may be able to see which of them grows. Same of course during he night, but I will not suggest to wake up every hour :P.
I shut down my pc every day. Also 16 gig of ram here, only sometimes having an issue, but I do know why.
Has to do with wine and some windows vst,
Do you maybe use LMMS and VST ?
Ctrl + Esc and then in the taskmanager killing the vst solves the problem for me.