Bug 303625 - Memory leak in plasma-desktop with Nvidia binary driver
Summary: Memory leak in plasma-desktop with Nvidia binary driver
Status: RESOLVED UPSTREAM
Alias: None
Product: plasma4
Classification: Plasma
Component: general (show other bugs)
Version: 4.8.4
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-16 18:45 UTC by Shmerl
Modified: 2014-01-21 05:35 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Valgrind log with memory leaks (229.41 KB, text/x-log)
2012-07-16 18:47 UTC, Shmerl
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Shmerl 2012-07-16 18:45:27 UTC
When using Nvidia closed driver (even the most recent beta 304.22), plasma-desktop gradually leaks memory, until it consumes all free RAM.

I run it with valgrind (see the attachment) which detects tons of definitive leaks.

OS: Debian testing, x86_64.
Kernel: 3.2.0-3
xserver-xorg-core: 1.12.1
GPU: Quadro FX 1600M/PCIe/SSE2
Driver: Nvidia closed driver 304.22

Reproducible: Always

Steps to Reproduce:
1. Log in, let the system run.

Actual Results:  
1. plasma-desktop eats RAM continuously.

Expected Results:  
1. plasma-desktop should not consume all RAM.
Comment 1 Shmerl 2012-07-16 18:47:35 UTC
Created attachment 72565 [details]
Valgrind log with memory leaks

Output of valgrind run of plasma-desktop filtered for memory leaks:

valgrind --tool=memcheck --leak-check=full plasma-desktop
Comment 2 Shmerl 2012-09-04 16:08:50 UTC
I tested the same scenario with some other Nvidia cards, and the bug doesn't happen except with Quadro FX 1600M. It could be hardware specific.
Comment 3 Shmerl 2012-09-05 23:09:44 UTC
I found the culprit setting which triggers the leak.

In the system tray clock > Digital Clock Settings > Appearance > Show seconds.

When it's on - the leak is active. When it's off - it's not leaking. Still it didn't manifest itself on other GPU (desktop, Nvidia 7300gs) for me. So it still can be KDE or Nvidia specific.
Comment 4 Shmerl 2012-09-27 15:54:19 UTC
This bug is fixed with Nvidia's driver 304.51.
Comment 5 John Aylward 2012-12-09 05:51:20 UTC
on KDE 4.9.3 using the nvidia binary I see a similar leak. Should I try to get a similar valgrind log? If so, what's the best way to start plasma desktop through valigrind. I usually login through kdm and don't start kde manually.
Comment 6 Shmerl 2012-12-09 05:55:53 UTC
I see that this bug is not entirely gone. The leak happens in Xorg process, but it's caused by plasma-desktop not releasing resources properly, which can be checked with xrestop:

See https://devtalk.nvidia.com/default/topic/524486/linux/memory-leak-in-xorg-with-quadro-fx-1600m-pcie-sse2/

To run plasma-desktop with valgrind just kill the plasma-desktop process, and run it through valgrind from the terminal (as here: https://bugs.kde.org/show_bug.cgi?id=303625#c1 ).
Comment 7 John Aylward 2012-12-09 16:17:37 UTC
I wasn't able to attach my log as it's was pretty large. Here's a link:
http://www.aylward.me/~john/plasma-desktop.leak.log

I ran it overnight with almost no user interaction. It ran for about 9.5 hours.