** Changed in: metacity (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to metacity in Ubuntu.
https://bugs.launchpad.net/bugs/774740
Title:
Huge memory leak in metacity
To manage no
I applied the patch #778727 on ubuntu 11.04 64-bit.
It does fix the memory leak problem (metacity used to consume ~4GB of mem while
with the patch never exceeds 5MB).
However, it introduces a new problem. Alt-tab functionality to switch between
processes is now broken.
Every time I press Alt-tab
I confirm this bug using 11.04 on a laptop with Radeon Mobility X600.
The temporary fix of comment 18 works as a charm: metacity memory consumption
just went from 283 MB to 14 MB!
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to metaci
temporary fix is (when metacity used mach memory)
metacity-message restart
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to metacity in Ubuntu.
https://bugs.launchpad.net/bugs/774740
Title:
Huge memory leak in metacity
To manage not
The attachment "Bug #774740.patch" of this bug report has been
identified as being a patch. The ubuntu-reviewers team has been
subscribed to the bug report so that they can review the patch. In the
event that this is in fact not a patch you can resolve this situation by
removing the tag 'patch' f
With valgrind log i found the leak and patch it, sameone know how push the
patch to main stream?
I insert the patch as attachment.
I use the patched version by 6 hours without restart and no memory usage
increase, before every 2-3 hours i must restart metacity.
** Patch added: "Bug #774740.pat
** Changed in: metacity (Ubuntu)
Status: Incomplete => In Progress
** Changed in: metacity (Ubuntu)
Assignee: (unassigned) => tglman (tglman)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to metacity in Ubuntu.
https://bugs
Yes, I definitely see redraw issues as well! Would be fantastic if they
were related and was solved by solving this issue :)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to metacity in Ubuntu.
https://bugs.launchpad.net/bugs/774740
Ti
There seems to be a relation to missing redraw rectangles and metacity
getting slower/collecting much memory.
Why does metacity collect so much pixmap memory?
** Attachment added: "xrestop output before and after metacity restart"
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/77474
I can also confirm this memory leak:
Architecture: amd64
Version: 1:2.30.3-0ubuntu8
I have to regularly reboot metacity with a laucher icon with 'metacity
--replace'.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to metacity in Ubuntu
I also confirm this memory leak. Ubuntu 11.04 64 bit
** Attachment added: "metacity-memleak.jpg"
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/774740/+attachment/2247249/+files/metacity-memleak.jpg
--
You received this bug notification because you are a member of Ubuntu
Desktop Bug
A temporary fix is, every few days (or when you swap space is nearly all
used up):
pkill metacity ; sleep 1 ; metacity
it saves one logging out or rebooting
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to metacity in Ubuntu.
https://
just saw this bug happening here as well.
I see you already have a valgrind log, do you need another?
is there anything else I can help with?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to metacity in Ubuntu.
https://bugs.launchpad.ne
Just killall'd it and ran it from the command line. Here you go.
** Attachment added: "valgrind-logs-metacity.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/774740/+attachment/2159696/+files/valgrind-logs-metacity.tar.gz
--
You received this bug notification because you are
What's the best way to get the valgrind log for Metacity? i.e. As it
auto-launches at login to X, how do I get X to call it through Valgrind?
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to metacity in Ubuntu.
https://bugs.la
we still need a valgrind log.
** Changed in: metacity (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to metacity in Ubuntu.
https://bugs.launchpad.net/bugs/774740
Title:
Huge memory lea
even worse after a few days... see attached photo
** Attachment added: "Screenshot-System Monitor-1.png"
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/774740/+attachment/2149489/+files/Screenshot-System%20Monitor-1.png
** Changed in: metacity (Ubuntu)
Status: Incomplete => Co
Same thing here. Screenshot attached, lshw output below.
$ uname -a
Linux trogdor 2.6.38-9-generic #43-Ubuntu SMP Thu Apr 28 15:23:06 UTC 2011
x86_64 x86_64 x86_64 GNU/Linux
$ sudo lshw -short
H/W path Device Class Description
==
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please try to obtain a valgrind log following the
instructions at https://wiki.ubuntu.com/Valgrind and attach the file to
the bug report. This will greatly help us in tracking down your problem.
** Changed in: met
** Summary changed:
- metacity memory usage
+ Huge memory leak in metacity
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to metacity in Ubuntu.
https://bugs.launchpad.net/bugs/774740
Title:
Huge memory leak in metacity
--
desktop
20 matches
Mail list logo