I don't know if this will help any of you, but running in a xgl session
seems to have fixed the memory leak with compiz. Now to figure out whats
going on with the streaming stuff.
Carl
--
memory leak with ring
https://bugs.launchpad.net/bugs/151168
You received this bug notification because you
Ah, so maybe I do have two separate leaks. I'll sit back and listen
until I learn more about how this all works.
Carl
--
memory leak with ring
https://bugs.launchpad.net/bugs/151168
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
Hi,
I agree with Matt, this problem does not seem to happen with the
nvidia/metacity combination. That doesn't mean that it is definitely a
compiz problem though - the "black windows" problem with earlier nvidia
drivers running out of video memory was only seen with beryl and nvidia.
Chris
M
On Tue, 2007-10-23 at 11:41 +, yellowbread wrote:
> Travis, that's my exactly my point. With the nvidia driver, I was
> seeing the same behavior as described here. While running top, I could
> see the resident memory used by compiz.real rising steadily. Then I
> removed the nvidia driver. Of
Travis, that's my exactly my point. With the nvidia driver, I was
seeing the same behavior as described here. While running top, I could
see the resident memory used by compiz.real rising steadily. Then I
removed the nvidia driver. Of course compiz.real was no longer one of
the running processes,
If you're not using the nvidia driver you're not using compiz so you
couldn't be seeing a 'memory leak in compiz'.
--
memory leak with ring
https://bugs.launchpad.net/bugs/151168
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
Don't be so quick to point the finger at nvidia. I removed the nvidia
drivers and found the same behavior. Often, not all the memory a window
uses gets freed upon closing the window, and streaming applications,
music, video, seem to leave behind about 20% of the data they process in
memory. In all
I've started a forum thread on nvnews about this issue; maybe someone
will report a workaround or something. and james jones an nvidia has
responded to an email on compiz.net & entered this bug into their
system. so maybe this'll get osme attention from them.
the nvidia forum url is :
http://ww
On Mon, 2007-10-22 at 18:26 +, tombrus wrote:
> Salvation seems near: on tweakers.net I just saw an update of the nvidia
> drivers to 100.14.23 (I currently have 100.14.19). The release
> highlights mention: "Fixed a problem with a Compiz after vt-switching".
>
i don't think that's our bug.
Salvation seems near: on tweakers.net I just saw an update of the nvidia
drivers to 100.14.23 (I currently have 100.14.19). The release
highlights mention: "Fixed a problem with a Compiz after vt-switching".
-Tom
--
memory leak with ring
https://bugs.launchpad.net/bugs/151168
You received this b
Seems this is a driver problem.
** Changed in: linux-restricted-modules-2.6.22 (Ubuntu)
Sourcepackagename: compiz => linux-restricted-modules-2.6.22
--
memory leak with ring
https://bugs.launchpad.net/bugs/151168
You received this bug notification because you are a member of Ubuntu
Bugs, which i
I can confirm this.
Running a HP Pavilion dv6106 Laptop with a Nvidia 6150 and nvidia-glx-
new.
I'm with tombrus that "medium" is to cafeful, and should be upped a bit,
as it seems to be affecting all people with the new nvidia drivers.
Then again this could be a bug in the new Nvidia drivers,
I've tried this, and it's not a problem with any plugin.
Under nvidia-glx-new, I ran compiz with no plugins enabled, spawned 100
gnome-terminals then killed them. compiz.real's shared memory size increased
by ~150Mb and didn't decrease on closing the terminals. Spawning another 100
terminals
Well, add another to the list.
I am running Gutsey on a HP DV2200 w/ a geforce go 7200 and I also get
this bug. I'm using custom effects from Compiz Fusion as well. System
Monitor shows compiz.real eating 330Virtual and 310 resident memory.
My memory keeps climbing and it will eventually get to
I agree with Tombrus, this appears to be a critical failure in Compiz.
Hopefully this will get fixed very quickly
tombrus wrote:
> Same here.
>
> Just upgraded from Feisty to Gutsy. When I maximize/minimize windows
> compiz eats my memory eagerly. I switched window resizing from the
> default 'ou
Same here.
Just upgraded from Feisty to Gutsy. When I maximize/minimize windows
compiz eats my memory eagerly. I switched window resizing from the
default 'outline' to 'normal' and that seems to worsen things: resizing
then also eats memory by the meg. I attached a log of 'ps aux' of compiz
each s
Same here.
I have an nvidea card, core2duo and 1GB ram. I've the upgrade from feisty
during the beta stage of gutsy.
Last night I had to shutdown the computer because compiz.real consumed all
memory and the machine turn unusable.
** Attachment added: "system monitor image"
http://launchpadl
what happens if you maximize/restore a window about 20 times?
https://bugs.freedesktop.org/show_bug.cgi?id=12613
also I believe that 50MB for a start is not normal by itself with
compiz-core&compiz-kde packages only?
** Attachment added: "screenshot of compiz memory leak with maximize/restore"
I should also add that the amount of memory leaked appears to be
(somewhat unsurprisingly) proportional to the size of the window.
That is to say, if I open and close a new firefox window, I see compiz
resident memory jump by ~10MB. With a smaller terminal window, it's ~3MB
as noted before.
--
m
Is it possible to change the title of this bug? Something like "compiz
leaks memory with NVIDIA proprietary driver" (or similar)?
I just filed a new bug about compiz leaking memory and I ignored this
one because the title said it only affected the Ring plugin which I
never use.
On my machine, it'
Same problem here, with an hp Pavilion dv2000, 1GB Ram, probably like
sampsa... Nothing special to say, only another feedback for this boring
situation!
militanz
--
memory leak with ring
https://bugs.launchpad.net/bugs/151168
You received this bug notification because you are a member of Ubuntu
On Tue, 2007-10-16 at 05:54 +, Danny Baumann wrote:
> Although I'm obviously biased (as the one who wrote ring), I have to say that
> I really, really doubt there is a leak that may fill several hundred
> megabytes of memory inside ring.
> Besides the usual boilerplate code that every compiz
Hi,
I'm not using ring, nor desktop cube - just the "extra effects" and top
shows my nvidia.real using the following virtual = 489M, Resident = 421M
and that's just over the course of three hours with no video playback.
Yesterday I experienced several restarts of the desktop and dmesg showed
proce
Although I'm obviously biased (as the one who wrote ring), I have to say that I
really, really doubt there is a leak that may fill several hundred megabytes of
memory inside ring.
Besides the usual boilerplate code that every compiz plugin has, there is only
one place of allocation where a 8 byt
24 matches
Mail list logo
