Bug#763193: kde-base: KDE Memory leak still present in jessie
As kde4libs are not in Bullseye anymore and phased out completely, we have moved to the KDE Frameworks generation of technology. This defect is potentially not relevant anymore as a lot of the technology is different now. At least it needs a new reproduction and thus confirmation that is is still present on Bullseye or Unstable/ Testing. My suggestion is to close the report, because there would have been more information meanwhile if a similar defect has shown in the last 9 years. Leslie thanks again for reporting this problem, sorry that it could not fixed for kde4libs based technology. (Or, by chance are you still using the new stuff and experiencing still such problems?)
Bug#763193: kde-base: KDE Memory leak still present in jessie
Resending the reply, I've sent privately by mistake. ¡Hola Leslie! There are some points that aren't clear in your mail, please clarify. El 2014-09-29 a las 10:47 -0500, Leslie Rhorer escribió: I then loaded the applications listed in the bug report, and went about the business of configuring the new system. When you say loaded, do you mean installed? Which desktop environment were you running? At some point, I activated KDE again, and left it running for a time, at which point I noted the memory usage was growing again. How did you check the memory consumption? Left overnight, the app consumed nearly 100% of the 8G of memory installed in this machine. Which app, and how did you check? Happy hacking, -- Brilliant opportunities are cleverly disguised as insolvable problems. -- Gardener's Philosophy The reverse is also true. -- Corollary Saludos /\/\ /\ `/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#763193: kde-base: KDE Memory leak still present in jessie
¡Hola Leslie! El 2014-09-29 a las 18:11 -0500, Leslie Rhorer escribió: On 9/29/2014 5:17 PM, Maximiliano Curia wrote: When you say loaded, do you mean installed? Yes. apt-get install xx. The list is in the bug report. Which desktop environment were you running? KDE 4.14.1. It's what ships with jessie. How did you check the memory consumption? A couple of different ways. `free` shows total usage, of course. free is completly useless here. `gnome-system-monitor` is a handy GUI based system info app. For example, right now, after being active few hours, kded4 is allocated 932 MiB, with only a Konsole session with 4 tabs and Gnome-system-monitor active. Compare that with KDE 4.4.5, running under Debian Squeeze on another machine that has had KDE up for days. It's using 35 MB. The entire system is only using 700 MB, and there are quite a few apps running. Ok, gnome-system-monitor shows the rss usage by default. A more detailed information can be obtained with (the following commands assume that there is only one kded4 running, if there are more, for different users, or whatever, please adapt the commands): $ pid=$(pidof kded4) $ ps u $pid | tee /tmp/kded4_leak USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND maxy 5568 0.0 2.0 1615380 160056 ? Sl Sep24 0:12 kdeinit4: kded4 [kdeinit] And use the pid to get information about the maps: $ cat /proc/$pid/smaps | tee -a /tmp/kded4_leak And pmap, just because it's easier to read than the plain smaps; $ pmap -x $pid | tee -a /tmp/kded4_leak Since its all text, compressing the /tmp/kded4_leak file before sending it as an attachment would be useful (some mail clients like kmail allow you the compress the attachment directly from it). You can produce a compressed /tmp/kded4_leak.gz with: $ gzip -9 /tmp/kded4_leak Could you please attach the produced file to this bug? Which app, and how did you check? Kded4, using Gnome-system-monitor. Perhaps notably, udisks-daemon does not seem to be swelling like it did under wheezy. Just in the time it has taken to write this message, kded4 has swollen to 950 MB. Happy hacking, -- Programs must be written for people to read, and only incidentally for machines to execute. -― Hal Abelson, Structure and Interpretation of Computer Programs Saludos /\/\ /\ `/ signature.asc Description: Digital signature
Bug#763193: kde-base: KDE Memory leak still present in jessie
On 9/30/2014 6:10 AM, Maximiliano Curia wrote: $ ps u $pid | tee /tmp/kded4_leak USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND maxy 5568 0.0 2.0 1615380 160056 ? Sl Sep24 0:12 kdeinit4: kded4 [kdeinit] And use the pid to get information about the maps: $ cat /proc/$pid/smaps | tee -a /tmp/kded4_leak And pmap, just because it's easier to read than the plain smaps; $ pmap -x $pid | tee -a /tmp/kded4_leak Since its all text, compressing the /tmp/kded4_leak file before sending it as an attachment would be useful (some mail clients like kmail allow you the compress the attachment directly from it). You can produce a compressed /tmp/kded4_leak.gz with: $ gzip -9 /tmp/kded4_leak Could you please attach the produced file to this bug? kded4_leak.gz Description: application/gzip
Bug#763193: kde-base: KDE Memory leak still present in jessie
On 9/28/2014 3:31 PM, Maximiliano Curia wrote: Control: force-merge -1 725116 ¡Hola Leslie! El 2014-09-28 a las 10:29 -0500, Leslie Rhorer escribió: This bug was present in wheezy and persists in jessie. It was previously reported under Bug#725116. Ok, merging the two bugs. Usually, if a bug has not been fixed, we prefer to have followups, instead of opening new bugs. Um, OK. Since it is a completely new release of the OS, I thought it would be prudent to open a new report against the new release. It's also been almost exactly a year sine I opened the original report, and this is the first time I have had any response on it. The behavior manifests when using XDMCP, but is not strictly related to KDE alone, becasue it is not present in a fresh install of the operating system from a netinst CD. In order for us to work on a bug, we need to have clear reproduction instructions. I loaded the netinst CD, selected Advanced, had the utility reformat the partitions, and completed the install. I used SSH to get into the system, loaded vim, created an automated SSH login, modified kdmrc and Xaccess to allow logins via XDMCP, set the network interface for a static IP, and rebooted the system. After that, I logged in via XDMCP, and ran a short test to see if the unrestricted growth was still an issue. It did not seem to be. I then loaded the applications listed in the bug report, and went about the business of configuring the new system. At some point, I activated KDE again, and left it running for a time, at which point I noted the memory usage was growing again. Left overnight, the app consumed nearly 100% of the 8G of memory installed in this machine. When first launched, the memory usage is generally in the 500M - 800M range. If there is a leak, it could be that there is a memory area that is not being correctly freed (valgrind can help detecting this) or that certain type of alive object increases but never decreases (a memory profiler might help with this). Can you be a bit more specific? I installed valgrind, but I am going to need some specific binaries against which to run the utility. Only after installing several other packages has the behavior mmanifested itself. The memory utilization has grown from 512MB to 4.5G over a period of 2 days. When you upgrade a program that is currently running, the linux kernel needs to load the old version in memory and it will stay there until the program ends. It could be, that if you upgraded the whole of kde and didn't restart your session this is the reason. I didn't upgrade anything. As I said in my report, this is a virgin install of jessie. What's more, KDE wasn't even running when I added the elements listed in the bug report. The system has been rebooted at handful of times since installing the OS. What's more, the bug report against wheezy was posted almost exactly a year ago, and the system has most certainly been rebooted since then. It could be that there is a leak, but in order to work on that we need more information. Indubitably, but I need to know what you need me to investigate so I can tell you what you need to know. I'm not a duffer, but I'm surely not a guru, either. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#763193: kde-base: KDE Memory leak still present in jessie
Package: kde-baseapps Version: 4:4.14.1-1 Severity: important File: kde-base Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.14-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages kde-baseapps depends on: ii dolphin 4:4.14.1-1 ii kde-baseapps-bin 4:4.14.1-1 ii kdepasswd 4:4.14.1-1 ii kfind 4:4.14.1-1 ii konqueror 4:4.14.1-1 ii konsole 4:4.14.1-1 ii kwrite4:4.14.1-1 ii plasma-widget-folderview 4:4.14.1-1 Versions of packages kde-baseapps recommends: ii konqueror-nsplugins 4:4.14.1-1 kde-baseapps suggests no packages. -- no debconf information This bug was present in wheezy and persists in jessie. It was previously reported under Bug#725116. The behavior manifests when using XDMCP, but is not strictly related to KDE alone, becasue it is not present in a fresh install of the operating system from a netinst CD. Only after installing several other packages has the behavior mmanifested itself. The memory utilization has grown from 512MB to 4.5G over a period of 2 days. Here is the list of software installed after the OS installation: Commandline: apt-get install vim Commandline: apt-get install gadmin-rsync Commandline: apt-get install dovecot-imapd Commandline: apt-get install nut Commandline: apt-get install nut Commandline: apt-get install gnome-disk-utility Commandline: apt-get install nmon Commandline: apt-get install ssmtp Commandline: apt-get install fetchmail Commandline: apt-get install ffmpeg Commandline: apt-get install samba Commandline: apt-get install winbind Commandline: apt-get install isc-dhcp-server Commandline: apt-get install gnome-system-monitor Commandline: apt-get install --reinstall python-pil Commandline: apt-get install libjpeg62 libjpeg62-dev Commandline: apt-get install libjpeg-dev Commandline: apt-get install libtiff-dev Commandline: apt-get install libfreetype6-dev Commandline: apt-get install cmake -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#763193: kde-base: KDE Memory leak still present in jessie
Control: force-merge -1 725116 ¡Hola Leslie! El 2014-09-28 a las 10:29 -0500, Leslie Rhorer escribió: This bug was present in wheezy and persists in jessie. It was previously reported under Bug#725116. Ok, merging the two bugs. Usually, if a bug has not been fixed, we prefer to have followups, instead of opening new bugs. The behavior manifests when using XDMCP, but is not strictly related to KDE alone, becasue it is not present in a fresh install of the operating system from a netinst CD. In order for us to work on a bug, we need to have clear reproduction instructions. If there is a leak, it could be that there is a memory area that is not being correctly freed (valgrind can help detecting this) or that certain type of alive object increases but never decreases (a memory profiler might help with this). Only after installing several other packages has the behavior mmanifested itself. The memory utilization has grown from 512MB to 4.5G over a period of 2 days. When you upgrade a program that is currently running, the linux kernel needs to load the old version in memory and it will stay there until the program ends. It could be, that if you upgraded the whole of kde and didn't restart your session this is the reason. It could be that there is a leak, but in order to work on that we need more information. Happy hacking, -- If you have too many special cases, you are doing it wrong. -- Craig Zarouni Saludos /\/\ /\ `/ signature.asc Description: Digital signature
