[ksmserver] [Bug 373274] ksmserver eats memory and does not lock screen

[Simon Andric]

https://bugs.kde.org/show_bug.cgi?id=373274

Simon Andric  changed:

   What|Removed |Added

 CC||simonandr...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[ksmserver] [Bug 373274] ksmserver eats memory and does not lock screen

[Stéphane ANCELOT]

https://bugs.kde.org/show_bug.cgi?id=373274

Stéphane ANCELOT  changed:

   What|Removed |Added

 CC||sance...@numalliance.com

--- Comment #10 from Stéphane ANCELOT  ---
Hi,
I can confirm this bug, too on intel J1900 platform / and plasma 5.8.6(opensuse
42.2).
after two days , the ksmserver uses 57% of ram.
Nobody uses the system.

The only thing I found in journalctl is oomkiller messages :

pt. 05 02:03:22 linux-qhf9 kernel: Killed process 1418 (plasmashell)
total-vm:3196376kB, anon-rss:74220kB, file-rss:15936kB
sept. 05 02:03:22 linux-qhf9 kernel: Purging GPU memory, 0 bytes freed, 5283840
bytes still pinned.
sept. 05 02:03:22 linux-qhf9 kernel: Qt bearer threa invoked oom-killer:
gfp_mask=0x201da, order=0, oom_score_adj=0
sept. 05 02:03:22 linux-qhf9 kernel: Qt bearer threa cpuset=/ mems_allowed=0
sept. 05 02:03:22 linux-qhf9 kernel: CPU: 2 PID: 1464 Comm: Qt bearer threa Not
tainted 3.18.20cobalt #1
sept. 05 02:03:22 linux-qhf9 kernel: Hardware name: To be filled by O.E.M. To
be filled by O.E.M./Aptio CRB, BIOS 5.6.5 02/04/2015
sept. 05 02:03:22 linux-qhf9 kernel:   880037504648
814252d9 880037504000
sept. 05 02:03:22 linux-qhf9 kernel:  81422c4d 0401
 
sept. 05 02:03:22 linux-qhf9 kernel:  8800a186faf8 
a02326b3 
sept. 05 02:03:22 linux-qhf9 kernel: Call Trace:
sept. 05 02:03:22 linux-qhf9 kernel:  [] ?
dump_stack+0x49/0x6a
sept. 05 02:03:22 linux-qhf9 kernel:  [] ?
dump_header.isra.8+0x73/0x1e0
sept. 05 02:03:22 linux-qhf9 kernel:  [] ?
i915_gem_shrinker_oom+0x179/0x1aa [i915]
sept. 05 02:03:22 linux-qhf9 kernel:  [] ?
_raw_spin_unlock_irqrestore+0xc/0x1f
sept. 05 02:03:22 linux-qhf9 kernel:  [] ?
oom_kill_process+0x70/0x322
sept. 05 02:03:22 linux-qhf9 kernel:  [] ?
has_ns_capability_noaudit+0x32/0x3d
sept. 05 02:03:22 linux-qhf9 kernel:  [] ?
out_of_memory+0x438/0x451
sept. 05 02:03:22 linux-qhf9 kernel:  [] ?
__alloc_pages_nodemask+0x5fa/0x641
sept. 05 02:03:22 linux-qhf9 kernel:  [] ?
radix_tree_lookup_slot+0x10/0x23
sept. 05 02:03:22 linux-qhf9 kernel:  [] ?
alloc_pages_current+0xaf/0xcc
sept. 05 02:03:22 linux-qhf9 kernel:  [] ?
filemap_fault+0x218/0x36c
sept. 05 02:03:22 linux-qhf9 kernel:  [] ?
__do_fault+0x33/0x82
sept. 05 02:03:22 linux-qhf9 kernel:  [] ?
do_read_fault.isra.84+0x18e/0x21a
sept. 05 02:03:22 linux-qhf9 kernel:  [] ?
apic_timer_interrupt+0x60/0x90
sept. 05 02:03:22 linux-qhf9 kernel:  [] ?
handle_mm_fault+0x14e/0x8e6
sept. 05 02:03:22 linux-qhf9 kernel:  [] ?
__do_page_fault+0x26a/0x34a
sept. 05 02:03:22 linux-qhf9 kernel:  [] ?
rcu_irq_exit+0xf/0x5f
sept. 05 02:03:22 linux-qhf9 kernel:  [] ?
__ipipe_do_IRQ+0x6f/0x7a
sept. 05 02:03:22 linux-qhf9 kernel:  [] ?
__ipipe_get_current_domain+0x5/0xd
sept. 05 02:03:22 linux-qhf9 kernel:  [] ?
__ipipe_get_current_domain+0x5/0xd
sept. 05 02:03:22 linux-qhf9 kernel:  [] ?
__ipipe_do_IRQ+0x75/0x7a
sept. 05 02:03:22 linux-qhf9 kernel:  [] ?
do_page_fault+0x37/0x5a
sept. 05 02:03:22 linux-qhf9 kernel:  [] ?
page_fault+0x22/0x60
sept. 05 02:03:22 linux-qhf9 kernel: Mem-Info:
sept. 05 02:03:22 linux-qhf9 kernel: Node 0 DMA per-cpu:
sept. 05 02:03:22 linux-qhf9 kernel: CPU0: hi:0, btch:   1 usd:   0
sept. 05 02:03:22 linux-qhf9 kernel: CPU1: hi:0, btch:   1 usd:   0
sept. 05 02:03:22 linux-qhf9 kernel: CPU2: hi:0, btch:   1 usd:   0
sept. 05 02:03:22 linux-qhf9 kernel: CPU3: hi:0, btch:   1 usd:   0
sept. 05 02:03:22 linux-qhf9 kernel: Node 0 DMA32 per-cpu:
sept. 05 02:03:22 linux-qhf9 kernel: CPU0: hi:  186, btch:  31 usd:  58
sept. 05 02:03:22 linux-qhf9 kernel: CPU1: hi:  186, btch:  31 usd: 169
sept. 05 02:03:22 linux-qhf9 kernel: CPU2: hi:  186, btch:  31 usd:  28
sept. 05 02:03:22 linux-qhf9 kernel: CPU3: hi:  186, btch:  31 usd:  49
sept. 05 02:03:22 linux-qhf9 kernel: Node 0 Normal per-cpu:
sept. 05 02:03:22 linux-qhf9 kernel: CPU0: hi:  186, btch:  31 usd:  29
sept. 05 02:03:22 linux-qhf9 kernel: CPU1: hi:  186, btch:  31 usd:  69
sept. 05 02:03:22 linux-qhf9 kernel: CPU2: hi:  186, btch:  31 usd:  30
sept. 05 02:03:22 linux-qhf9 kernel: CPU3: hi:  186, btch:  31 usd:  59
sept. 05 02:03:22 linux-qhf9 kernel: active_anon:771616 inactive_anon:54480
isolated_anon:0
  active_file:96 inactive_file:85
isolated_file:0
  unevictable:127551 dirty:0 writeback:0
unstable:0
  free:6727 slab_reclaimable:3261
slab_unreclaimable:7521
  mapped:34939 shmem:58310 pagetables:7377
bounce:0
  free_cma:0
sept. 05 02:03:22 linux-qhf9 kernel: Node 0 DMA free:15352kB min:28kB low:32kB

[ksmserver] [Bug 373274] ksmserver eats memory and does not lock screen

[David Edmundson]

https://bugs.kde.org/show_bug.cgi?id=373274

David Edmundson  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED
 CC||k...@davidedmundson.co.uk

--- Comment #9 from David Edmundson  ---
Output handling was changing in 5.8.7 onwards.

Please reopen if you still have this issue.

-- 
You are receiving this mail because:
You are watching all bug changes.

[ksmserver] [Bug 373274] ksmserver eats memory and does not lock screen

[Anguo]

https://bugs.kde.org/show_bug.cgi?id=373274

Anguo  changed:

   What|Removed |Added

 CC||kde_b...@overshoot.tv

-- 
You are receiving this mail because:
You are watching all bug changes.

[ksmserver] [Bug 373274] ksmserver eats memory and does not lock screen

[Patrick Rudolph]

https://bugs.kde.org/show_bug.cgi?id=373274

--- Comment #8 from Patrick Rudolph  ---
I could reproduce the issue:
Moving the mouse over plasmashell's tray icons or startmenu entries causes the
memory in ksmserver to rise.

By looking at plasmashell's output I found thousands of "_xgeWireToEvent:
Unknown extension 148, this should never happen.".

By redirecting plasmashell's output to /dev/null the issue no longer occurs.

It looks like ksmserver doesn't read/discard the spawned child's output, but
collects them in some internal buffer.

The hotfix for me is to install libXext 1.3.3. But it just covers the bug, as
other applications could spam a lot and cause a memory bloat in ksmserver.

-- 
You are receiving this mail because:
You are watching all bug changes.

[ksmserver] [Bug 373274] ksmserver eats memory and does not lock screen

[Patrick Rudolph]

https://bugs.kde.org/show_bug.cgi?id=373274

Patrick Rudolph  changed:

   What|Removed |Added

 CC||patrick.rudolph@br-automati
   ||on.com

--- Comment #7 from Patrick Rudolph  ---
I've noticed this issue on several of out test system. We are using 
plasma-workspace 5.8.6 on Intel Skylake based platforms.

Usually the memory grows a few hundreds of byte per minute.
Sometimes it grows much faster.
No special processes are running, just plain KDE desktop.

The issue wasn't observed on other (older) Intel platforms.
The issue wasn't observed in case the desktop is started on a VNC session.

I noticed that stopping the plasmashell process (using SIGSTOP) stops the
ksmserver memory from growing. I suspect it's some kind of bug in the
plasmashell that only exists on some display drivers.

As the display driver might be related adding some debug infos:
* Mesa
* Vendor: Intel Open Source Technology Center (0x8086)
* Device: Mesa DRI Intel(R) HD Graphics 530 (Skylake GT2)  (0x1912)
* Version: 17.0.4
* modeset driver

-- 
You are receiving this mail because:
You are watching all bug changes.

[ksmserver] [Bug 373274] ksmserver eats memory and does not lock screen

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=373274

ludo...@gmx.com changed:

   What|Removed |Added

 CC||ludo...@gmx.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[ksmserver] [Bug 373274] ksmserver eats memory and does not lock screen

[Fincer]

https://bugs.kde.org/show_bug.cgi?id=373274

Fincer  changed:

   What|Removed |Added

 CC||fince...@hotmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[ksmserver] [Bug 373274] ksmserver eats memory and does not lock screen

[Christoph Feck]

https://bugs.kde.org/show_bug.cgi?id=373274

Christoph Feck  changed:

   What|Removed |Added

 CC||kde_...@dlk.pl

--- Comment #6 from Christoph Feck  ---
*** Bug 378551 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[ksmserver] [Bug 373274] ksmserver eats memory and does not lock screen

[Matthias]

https://bugs.kde.org/show_bug.cgi?id=373274

Matthias  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #5 from Matthias  ---
*** This bug has been confirmed by popular vote. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[ksmserver] [Bug 373274] ksmserver eats memory and does not lock screen

[Nick Cross]

https://bugs.kde.org/show_bug.cgi?id=373274

Nick Cross  changed:

   What|Removed |Added

 CC||k...@goots.org

-- 
You are receiving this mail because:
You are watching all bug changes.

[ksmserver] [Bug 373274] ksmserver eats memory and does not lock screen

[Craig Conner]

https://bugs.kde.org/show_bug.cgi?id=373274

Craig Conner  changed:

   What|Removed |Added

 CC||fuznaci...@gmail.com

--- Comment #4 from Craig Conner  ---
Confirmed, ksmserver on my desktop is using about 6.9 GB RAM right now...  I've
only been logged in for about two hours.

I also happen to use Fedora, and this persists in package
plasma-workspace-5.8.6

# rpm -q --whatprovides /usr/bin/ksmserver
plasma-workspace-5.8.6-6.fc25.x86_64


KiB Mem : 16400052 total,  3828064 free,  9202236 used,  3369752 buff/cache
  PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND 
 7943 fuzzy 39  19  9.875g 6.756g  23496 S   0.0 43.2   4:26.76 ksmserver


...or, as another person expressed it,

# ps -eo rss,pid,user,command --sort -rss | awk '{ hr=$1/1024 ; printf("%13.2f
Mb ",hr) } { for ( x=4 ; x<=NF ; x++ ) { printf("%s ",$x) } print "" }' | head
-n2
 0.00 Mb COMMAND 
  6918.64 Mb /usr/bin/ksmserver


My system:
Intel(R) Core(TM) i5-3550 CPU @ 3.30GHz,16 GB RAM, and in case it's relevant,
nvidia GTX 1060 (6GB) (and nvidia's drivers, version 375.39)

-- 
You are receiving this mail because:
You are watching all bug changes.

[ksmserver] [Bug 373274] ksmserver eats memory and does not lock screen

[gianogli]

https://bugs.kde.org/show_bug.cgi?id=373274

gianogli  changed:

   What|Removed |Added

 CC||giano...@tiscali.it

--- Comment #3 from gianogli  ---
I can confirm this bug.
After 15 days, in my workstation, the ksmserver process is using 20GB of RAM.
Is there a way to debug this leak?
Thanks...

I'm using Debian Testing with plasma-workspace 4:5.8.4-1 (amd64).

-- 
You are receiving this mail because:
You are watching all bug changes.

[ksmserver] [Bug 373274] ksmserver eats memory and does not lock screen

[Potomac]

https://bugs.kde.org/show_bug.cgi?id=373274

Potomac  changed:

   What|Removed |Added

 CC||mister.free...@laposte.net

--- Comment #2 from Potomac  ---
I can confirm this bug,

randomly after several hours ksmserver eats too much ram, for example on
systems with 4 Gb ram ksmserver can eat 3 Gb, which can cause swap disk
operatin, and slowdown the PC,

I use archlinux 64 bits, plasma 5.9.3-1

-- 
You are receiving this mail because:
You are watching all bug changes.

[ksmserver] [Bug 373274] ksmserver eats memory and does not lock screen

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=373274

--- Comment #1 from johann.jacobs...@directbox.com ---
This problem persists in 5.8.5

-- 
You are receiving this mail because:
You are watching all bug changes.