dx-packages team mailing list archive
-
dx-packages team
-
Mailing list archive
-
Message #30090
[Bug 1061792] Re: Memory Leak in Unity (Compiz)
[Expired for unity (Ubuntu) because there has been no activity for 60
days.]
** Changed in: unity (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1061792
Title:
Memory Leak in Unity (Compiz)
Status in Unity:
Expired
Status in unity package in Ubuntu:
Expired
Bug description:
There seems to be a memory leak in Unity that comes with use (not
age).
Hardware: ThinkPad W510 (nVidia Quadro FX 880M, driver 304.51), Core2
-Duo-based desktop with nVidia 560Ti (same driver)
Software: Quantal Beta, up-to-the-moment updates, both 64- and 32-bit
(one of each).
*Note: I can *not* test with nouveau. Not only is it completely
unsuitable for laptops due to terrible power management, but neither
computer will boot with it - I get the PFIFO stuff, even though the
-16 kernel was supposed to fix that.
Steps to reproduce:
1) Log into Unity and launch System Monitor (gnome-system-monitor).
Set to view "all processes" and organize by the "memory" column. Take
note of the amount of RAM taken by the Compiz and Xorg processes.
2) Open a bunch of programs. I use: Nautilus, Gnome-Terminal, Chrome,
Banshee, EasyTag, EasyMP3Gain, Empathy, Eclipse, and Rhythmbox.
3) Close all of the programs except gnome-system-monitor. Note the
increase in RAM the Compiz and Xorg processes take.
4) Repeat steps 3-4. Memory on each process steadily rises.
It isn't by a lot, but it creates an environment wherein the longer
one uses one's Unity session, the less free RAM one has to work with
(as neither process ever seems to give up any of its RAM, ever, not
even after 10 hours of use).
I don't seem to have any stability or performance issues stemming from
this.
ALSO: Opening the dash at all raises the RAM usage by a LOT, and
subsequent openings of the dash (poking around, clicking on new
buttons that reveal icons I haven't seen before, etc) also grows the
process's RAM. By a LOT on the first run, but by a noticeable amount
on later runs.
*I* think this is a pretty high-priority issue, but as the RAM use and
growth isn't all THAT large (~0.5/1 MiB every time steps 2-3 are
repeated), I could understand if it weren't marked critical... but I
think any leak is critical, so there's my bias.
STEALTH EDIT: I want to point out that just leaving the system logged
in does not cause Unity *or* Xorg to use more RAM over time. Not even
with the indicator-multiload running.
STEALTH EDIT #2: All lenses and scopes except the Application lens have been uninstalled, and do not factor into this. So I'm pretty sure we don't have a runaway call in any indexer or anything like it.
---
ApportVersion: 2.6.1-0ubuntu1
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
DistroRelease: Ubuntu 12.10
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20120926)
NonfreeKernelModules: nvidia
Package: unity 6.8.0-0ubuntu1
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 3.5.0-17.26-generic 3.5.5
Tags: quantal third-party-packages
Uname: Linux 3.5.0-17-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1061792/+subscriptions