| 2012-10-04 18:13:30 |
GonzO |
bug |
|
|
added bug |
| 2012-10-04 18:14:51 |
GonzO |
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)
*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. |
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. |
|
| 2012-10-04 18:42:19 |
GonzO |
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. |
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. See bug #982434 for more info about that, but I have a suspicion that this leak and that one are the same...
*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. |
|
| 2012-10-04 18:52:29 |
GonzO |
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. See bug #982434 for more info about that, but I have a suspicion that this leak and that one are the same...
*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. |
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. |
|
| 2012-10-05 02:37:07 |
Daniel van Vugt |
bug task added |
|
unity (Ubuntu) |
|
| 2012-10-05 02:37:18 |
Daniel van Vugt |
unity: status |
New |
Incomplete |
|
| 2012-10-05 02:37:22 |
Daniel van Vugt |
unity (Ubuntu): status |
New |
Incomplete |
|
| 2012-10-05 03:42:23 |
GonzO |
tags |
|
apport-collected quantal third-party-packages |
|
| 2012-10-05 03:42:25 |
GonzO |
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. |
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 |
|
| 2012-10-05 03:42:26 |
GonzO |
attachment added |
|
Dependencies.txt https://bugs.launchpad.net/bugs/1061792/+attachment/3374329/+files/Dependencies.txt |
|
| 2012-10-05 03:42:28 |
GonzO |
attachment added |
|
GconfCompiz.txt https://bugs.launchpad.net/bugs/1061792/+attachment/3374330/+files/GconfCompiz.txt |
|
| 2012-10-05 03:42:30 |
GonzO |
attachment added |
|
ProcEnviron.txt https://bugs.launchpad.net/bugs/1061792/+attachment/3374331/+files/ProcEnviron.txt |
|
| 2012-10-05 03:59:58 |
Daniel van Vugt |
unity: status |
Incomplete |
New |
|
| 2012-10-05 04:00:02 |
Daniel van Vugt |
unity (Ubuntu): status |
Incomplete |
New |
|
| 2012-10-20 12:22:36 |
Launchpad Janitor |
unity (Ubuntu): status |
New |
Confirmed |
|
| 2012-10-23 11:54:31 |
timbo |
bug |
|
|
added subscriber timbo |
| 2013-09-14 17:00:14 |
James Ramsay |
unity: status |
New |
Confirmed |
|
| 2013-09-15 01:46:19 |
Stephen M. Webb |
unity (Ubuntu): importance |
Undecided |
High |
|
| 2013-09-15 01:46:22 |
Stephen M. Webb |
unity: importance |
Undecided |
High |
|
| 2013-09-15 01:46:25 |
Stephen M. Webb |
unity: status |
Confirmed |
Triaged |
|
| 2013-09-15 01:46:27 |
Stephen M. Webb |
unity (Ubuntu): status |
Confirmed |
Triaged |
|
| 2013-10-31 02:16:36 |
bruno |
bug |
|
|
added subscriber bruno |
| 2013-12-09 13:45:22 |
Barta Tamás |
bug |
|
|
added subscriber Barta Tamás |
| 2014-12-05 16:37:11 |
Andrea Azzarone |
unity: status |
Triaged |
Incomplete |
|
| 2014-12-05 16:37:15 |
Andrea Azzarone |
unity (Ubuntu): status |
Triaged |
Incomplete |
|
| 2015-03-17 04:17:46 |
Launchpad Janitor |
unity (Ubuntu): status |
Incomplete |
Expired |
|
| 2015-03-17 04:17:49 |
Launchpad Janitor |
unity: status |
Incomplete |
Expired |
|
