Welcome, Guest. Please login or register.
Did you miss your activation email?

Author Topic:  Massive Memory Leak with plasma-workspace 5.4.x  (Read 5662 times)

tux

  • Guest
Massive Memory Leak with plasma-workspace 5.4.x
« on: 2015/09/13, 09:13:21 »
It seems that plasmashell use whole memory (RAM+swap), if you have plasma-workspace 5.4.x installed.

belze

  • Guest
Re: Massive Memory Leak with plasma-workspace 5.4.x
« Reply #1 on: 2015/09/13, 10:21:18 »
Are you using kdenext or debian's packages?

Offline piper

  • User
  • Posts: 1.785
  • we are the priests ... of the temples of syrinx
Re: Massive Memory Leak with plasma-workspace 5.4.x
« Reply #2 on: 2015/09/13, 14:20:02 »
I am not seeing this

Free speech isn't just fucking saying what you want to say, it's also hearing what you don't want to fucking hear

I either give too many fucks or no fucks at all, it's like I cannot find a middle ground for a moderate fuck distribution, it's like what the fuck

Offline devil

  • Administrator
  • User
  • *****
  • Posts: 4.838
Re: Massive Memory Leak with plasma-workspace 5.4.x
« Reply #3 on: 2015/09/13, 14:23:45 »
It is only virtual memory, which costs nothing at all.

For a better understanding, read http://serverfault.com/questions/138427/top-what-does-virtual-memory-size-mean-linux-ubuntu


greetz
devil

tux

  • Guest
Re: Massive Memory Leak with plasma-workspace 5.4.x
« Reply #4 on: 2015/09/13, 14:48:12 »
You can see memory leak on this picture, if you want.

Offline piper

  • User
  • Posts: 1.785
  • we are the priests ... of the temples of syrinx
Re: Massive Memory Leak with plasma-workspace 5.4.x
« Reply #5 on: 2015/09/13, 15:01:10 »
You haven't answered belze's question yet

How did you install kde ?

With or without kde-next ?

If kde-next, is repo still enabled ?
Free speech isn't just fucking saying what you want to say, it's also hearing what you don't want to fucking hear

I either give too many fucks or no fucks at all, it's like I cannot find a middle ground for a moderate fuck distribution, it's like what the fuck

tux

  • Guest
Re: Massive Memory Leak with plasma-workspace 5.4.x
« Reply #6 on: 2015/09/13, 15:05:09 »
With kdenext and kdenext repo is still enabled. This package is from Debian repo.

Offline piper

  • User
  • Posts: 1.785
  • we are the priests ... of the temples of syrinx
Re: Massive Memory Leak with plasma-workspace 5.4.x
« Reply #7 on: 2015/09/13, 15:18:50 »
Your gonna have to get rid of (disable kdenext)  that repo for now (unless things have changed that I am not aware of) and use debian's repo's.

Have you read any of the posts here

http://forum.siduction.org/index.php?topic=5719.0

Free speech isn't just fucking saying what you want to say, it's also hearing what you don't want to fucking hear

I either give too many fucks or no fucks at all, it's like I cannot find a middle ground for a moderate fuck distribution, it's like what the fuck

Offline drb

  • User
  • Posts: 165
Re: Massive Memory Leak with plasma-workspace 5.4.x
« Reply #8 on: 2015/09/13, 23:01:41 »
That thread says you shouldn't disable kdenext (santa) although it was suggested by someone you could try it (piper).

holgerw

  • Guest
Re: Massive Memory Leak with plasma-workspace 5.4.x
« Reply #9 on: 2015/09/13, 23:08:22 »
Hello,

in this case I want to read a statement from our siduction kde packager @Santa.

Some days ago I've made the experience, that with enabled kdenext not so much stuff should be removed than without kdenext. But this was tested by me on a system, which was installed and upgraded with enabled kdenext repo.

Maybe the situation is another, when setting up a fresh siduction system without kdenext.

Kind regards,
  Holger

Offline piper

  • User
  • Posts: 1.785
  • we are the priests ... of the temples of syrinx
Re: Massive Memory Leak with plasma-workspace 5.4.x
« Reply #10 on: 2015/09/13, 23:45:23 »
This is a build (built by me) without kdenext. (all 4 of my machines are running this build).

I don't have a massive memory leak with plasma-workspace

Now, I myself, cannot blame kdenext, as none of my 4 boxes are using it.

I also highly doubt it has anything to do with kdenext. it can be a magnitude of multiple problem(s)  of packages, configs, removed /packages/libs, etc.



Code: [Select]
System:    Host: x1 Kernel: 4.1.6-towo.1-siduction-amd64 x86_64 (64 bit) Desktop: KDE Plasma 5.4.1
           Distro: siduction 15.1.0 Thunderstruck - xorg - (201509110914)
Machine:   Mobo: Gigabyte model: GA-970A-UD3 v: x.x Bios: Award v: F7 date: 10/22/2012
CPU:       Hexa core AMD FX-6300 Six-Core (-MCP-) cache: 12288 KB
           clock speeds: max: 3500 MHz 1: 1400 MHz 2: 1400 MHz 3: 3000 MHz 4: 1400 MHz 5: 1400 MHz 6: 1400 MHz
Graphics:  Card: NVIDIA GF106 [GeForce GTS 450]
           Display Server: X.Org 1.17.2 driver: nvidia Resolution: 1920x1200@59.95hz
           GLX Renderer: GeForce GTS 450/PCIe/SSE2 GLX Version: 4.5.0 NVIDIA 352.21
Audio:     Card-1 NVIDIA GF106 High Definition Audio Controller driver: snd_hda_intel
           Card-2 Advanced Micro Devices [AMD/ATI] SBx00 Azalia (Intel HDA) driver: snd_hda_intel
           Sound: Advanced Linux Sound Architecture v: k4.1.6-towo.1-siduction-amd64
Network:   Card: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller driver: r8169
           IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: 90:2b:34:a5:99:2d
Drives:    HDD Total Size: 8001.6GB (24.9% used) ID-1: /dev/sda model: Hitachi_HDS72202 size: 2000.4GB
           ID-2: /dev/sdb model: ST3000DM001 size: 3000.6GB ID-3: /dev/sdc model: ST3000DM001 size: 3000.6GB
Partition: ID-1: / size: 199G used: 9.9G (6%) fs: ext4 dev: /dev/sda3
           ID-2: swap-1 size: 4.29GB used: 0.00GB (0%) fs: swap dev: /dev/sda1
Sensors:   System Temperatures: cpu: 30.0C mobo: 18.8C gpu: 35C
           Fan Speeds (in rpm): cpu: 2129 fan-2: 0 fan-3: 0 fan-5: 0
Info:      Processes: 212 Uptime: 2:05 Memory: 1521.0/7971.5MB Client: Shell (bash) inxi: 2.2.28
System:    Host: x1 Kernel: 4.1.6-towo.1-siduction-amd64 x86_64 (64 bit gcc: 5.2.1)
           Desktop: KDE Plasma 5.4.1 dm: sddm,sddm Distro: siduction 15.1.0 Thunderstruck - xorg - (201509110914)
Repos:     Active apt sources in file: /etc/apt/sources.list.d/debian.list
           deb http://httpredir.debian.org/debian/ unstable main contrib non-free
           Active apt sources in file: /etc/apt/sources.list.d/misc.list
           deb http://packages.siduction.org/extra experimental main contrib non-free
           deb http://packages.siduction.org/user experimental main contrib non-free
           deb http://packages.siduction.org/user unstable main
           Active apt sources in file: /etc/apt/sources.list.d/multimedia.list
           deb http://www.deb-multimedia.org sid main non-free
           Active apt sources in file: /etc/apt/sources.list.d/siduction.list
           deb http://liquorix.net/siduction/base unstable main
           deb http://liquorix.net/siduction/extra unstable main
           deb http://liquorix.net/siduction/fixes unstable main contrib non-free
Free speech isn't just fucking saying what you want to say, it's also hearing what you don't want to fucking hear

I either give too many fucks or no fucks at all, it's like I cannot find a middle ground for a moderate fuck distribution, it's like what the fuck

tux

  • Guest
Re: Massive Memory Leak with plasma-workspace 5.4.x
« Reply #11 on: 2015/09/14, 15:56:48 »
Are you using plasma-nm? Maybe it is reason why this memory leak occurred. 

Offline devil

  • Administrator
  • User
  • *****
  • Posts: 4.838
Re: Massive Memory Leak with plasma-workspace 5.4.x
« Reply #12 on: 2015/09/14, 16:13:48 »
I use it and have no leak. 3,1% atm.


greetz
devil

tux

  • Guest
Re: Massive Memory Leak with plasma-workspace 5.4.x
« Reply #13 on: 2015/10/04, 06:21:36 »
I have just re-enabled kdenext as Santa suggested and same memory leak is still here.

Offline dibl

  • siduction community member
  • Global Moderator
  • User
  • *****
  • Posts: 2.345
    • Land of the Buckeye
Re: Massive Memory Leak with plasma-workspace 5.4.x
« Reply #14 on: 2015/10/04, 12:35:04 »
I haven't seen it.  On a fully updated laptop using KF5 from debian sid (no kdenext repo), here is the status after 1 hour of runtime:






Code: [Select]
root@hp-350g:/# apt-cache policy plasma-workspace
plasma-workspace:
 Installed: 4:5.4.1-1
 Candidate: 4:5.4.1-1
 Version table:
*** 4:5.4.1-1 0
       500 http://httpredir.debian.org/debian/ unstable/main amd64 Packages
       100 /var/lib/dpkg/status


This is same laptop as here.


In your screenshot I can see your uptime was 7 hours.  How long does it take for plasmashell to use all that memory?  Classic memory leak problems on released software usually creep up fairly slowly -- that is why I let mine run an hour before checking it. But it never changed much from the time I first logged in. Since no one else appears to be seeing this issue, it seems to point toward something unique in your configuration.  Did you change any default settings related to the plasma desktop or video performance?
System76 Oryx Pro, Intel Core i7-11800H, SSD 970 EVO Plus;  Asus ROG STRIX X299-E, Core i7-7740X, Nvidia GTX-1060, dual monitors, SSD 860 EVO