Bug 378551

Summary: ksmserver - high memory usage - 1,9GB for ksmserver
Product: [Plasma] ksmserver Reporter: kolorafa <kde_org>
Component: generalAssignee: Lubos Lunak <l.lunak>
Status: RESOLVED DUPLICATE    
Severity: minor    
Priority: NOR    
Version: 5.9.2   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed In:

Description kolorafa 2017-04-08 09:56:56 UTC
1,891GB for ksmserver.

Overall it's not a problem, and i will update this box in few days, but I'm curious about what could be the cause of this. 

Maybe it's related that i use caffeine manually set to disable screen lockdown. This pc for some time now only shows and records camera feeds from home, it has 12G of ram as it was my previous workstation, but totally wasting it :D

The problem doesn't occure on my new workstation with plasma 5.9.4, but maybe someone have a few teories why could be the reason :)

Keep up the great work!

GiB RAM : 40,3/11,738 
GiB Swap:  0,0/0,000

  PID UŻYTK.   PR  NI    WIRT    REZ  %CPU %PAM     CZAS+ S KOMENDA                                                                        
 1056 kolorafa  20   0 2614,2m 1,891g   0,0 16,1   4:44.34 S ksmserver                                                                      
 1068 kolorafa  20   0  0,255t 522,0m   3,3  4,3 558:09.90 R plasmashell                                                                    
 1178 kolorafa  20   0 3044,1m 220,3m   0,0  1,8  13:03.16 S dropbox                                                                        
  407 root      20   0 1849,8m 169,6m  59,6  1,4   5265:45 S xeoma                                                                          
25151 kolorafa  20   0  279,3m 157,1m   0,0  1,3  24:34.39 S synergyc                                                                       
 1063 kolorafa  20   0 3208,9m 151,6m   7,9  1,3 586:43.72 R kwin_x11                                                                       
24201 kolorafa  20   0  622,4m 150,1m  47,0  1,2   4044:14 S xeoma
Comment 1 Christoph Feck 2017-04-21 19:45:06 UTC

*** This bug has been marked as a duplicate of bug 373274 ***