Summary: | kded4 and plasma-desktop aquire huge amounts of virtual memory, causing massive paging | ||
---|---|---|---|
Product: | [I don't know] kde | Reporter: | Gunter Ohrner <kdebugs> |
Component: | general | Assignee: | Unassigned bugs mailing-list <unassigned-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | lamarque, miklcct, odi |
Priority: | NOR | ||
Version: | 4.6 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Gunter Ohrner
2011-04-01 02:15:12 UTC
After upgrading my Qt from 4.6 to 4.7, plasma-desktop allocates more than 2 GiB of my virtual memory space! This make the machine not have enough virtual memory left for running a Java app. My machine is running Debian Wheezy with KDE 4.4.5 michael@debian:~/src/misc$ ps -A v | grep plasma-desktop 18532 ? Sl 0:12 4 2 2901853 62056 1.6 /usr/bin/plasma-desktop *** This bug has been marked as a duplicate of bug 206317 *** I'm not convinced that this is actually a duplicate of bug 206317. The symptoms seemt to be the same, but I used Kubuntu 9.10 with KDE 4.3.x before, - which should also be affected according to some of the comments in bug 206317 - and never experienced this behaviour before. It all started when I upgraded KDE, QT and its whole ecosystem to the versions contained in (K)Ubuntu Natty... Probably what the original report means is that it creates a 2GB mmap. /proc/pid/maps: 7fa2e7f1c000-7fa367f1c000 rwxp 00000000 00:00 0 /proc/pid/smaps: 7fa2e7f1c000-7fa367f1c000 rwxp 00000000 00:00 0 Size: 2097152 kB Rss: 2936 kB Pss: 2936 kB Shared_Clean: 0 kB Shared_Dirty: 0 kB Private_Clean: 0 kB Private_Dirty: 2936 kB Referenced: 2140 kB Anonymous: 2936 kB AnonHugePages: 2048 kB Swap: 0 kB KernelPageSize: 4 kB MMUPageSize: 4 kB Locked: 0 kB VmFlags: rd wr ex mr mw me nr It would be nice to know what this 2GB mapping is... Possibly it's the garbage collected heap of the javascript implementation of webkit. Please note that this is just reserved address space in the process which is mostly mapped to the zero page. So it doesn't actually use physical memory (RSS is only 3MB) until touched by actual data. |