Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 208341 - compiz and X leak memory when computer idle
Summary: compiz and X leak memory when computer idle
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: AMD64 Linux
: High normal (vote)
Assignee: Desktop-Effects herd
URL:
Whiteboard:
Keywords:
: 237502 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-01-31 19:41 UTC by Daniel G
Modified: 2009-03-07 16:54 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
A few top lines when it starts, X starts eating memory (top_start,51.11 KB, text/plain)
2008-01-31 19:55 UTC, Daniel G
Details
compiz leaks almost 3g res memory (top_before_death,50.88 KB, text/plain)
2008-01-31 19:56 UTC, Daniel G
Details
/var/log/messages time of error (messages,72.29 KB, text/plain)
2008-01-31 19:57 UTC, Daniel G
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel G 2008-01-31 19:41:58 UTC
Using compiz 0.6.2-r1,compiz-fusion 0.6.0,xorg-server 1.3.0.0-r4 with latest nvidia-driver 169.09 there appears a memory leak in the compiz and X processes. Unfortunately, both times it happened the kernel killed them with no way for me to debug.
I have set up a crontab to output a simple top output every five minutes to find it.
Attached are an excerpt from /var/log/messages and from the top output.
Can someone tell me the best procedure to make them coredump once this happens automatically?
Comment 1 Daniel G 2008-01-31 19:55:19 UTC
Created attachment 142311 [details]
A few top lines when it starts, X starts eating memory
Comment 2 Daniel G 2008-01-31 19:56:20 UTC
Created attachment 142313 [details]
compiz leaks almost 3g res memory

This is the point where compiz helps X eat up all system memory
Comment 3 Daniel G 2008-01-31 19:57:17 UTC
Created attachment 142315 [details]
/var/log/messages time of error

These are the messages on /var/log/messages when processes fail to get memory.
Comment 4 Gianluca Andreotti (K.a.o.s.) 2008-09-10 08:07:15 UTC
I have the same problem with an Intel 965gm.

x11-base/xorg-server-1.5.0
x11-drivers/xf86-video-i810-2.4.2-r1
x11-wm/compiz-0.7.6-r2
Comment 5 Jorge Manuel B. S. Vicetto (RETIRED) Gentoo Infrastructure gentoo-dev 2008-11-02 04:15:19 UTC
Please test it with compiz-0.7.8.
Comment 6 Jorge Manuel B. S. Vicetto (RETIRED) Gentoo Infrastructure gentoo-dev 2008-11-02 04:41:57 UTC
*** Bug 237502 has been marked as a duplicate of this bug. ***
Comment 7 Gianluca Andreotti (K.a.o.s.) 2008-11-12 18:41:34 UTC
(In reply to comment #5)
> Please test it with compiz-0.7.8.
> 

I still have the problem, also with Compiz git
Comment 8 Jorge Manuel B. S. Vicetto (RETIRED) Gentoo Infrastructure gentoo-dev 2008-11-13 18:38:14 UTC
Can you please open an upstream bug about this and put the link here?
Comment 9 Gustavo Felisberto (RETIRED) gentoo-dev 2008-11-16 17:17:45 UTC
I suffered alot from memory leaks in the 0.6 versions (even the git versions at the time). 

Right now with xorg-server-1.5.2, compiz 0.7.8 and nvidia-drivers 177.80 all seems better.

Use fusion-icon to start compiz and there select Loose Bindig and Indirect Rendering. These gave me the best FPS.
Comment 10 Scott Moreau 2008-11-21 13:11:48 UTC
Compiz has been scrutinized for memory leaks and all found have been fixed. The nvidia drivers on the other hand are notorious for memory leaks and could be part of the issue here. If you seem to be affected by this problem, please make sure to include which driver version you are using as well. It is recommended to use compiz 0.7.4 or greater but again, compiz is not known to leak memory at all. Further, I agree with Jorge Manuel B. S. Vicetto. Please make a report at bugs.freedesktop.org and post the link here.
Comment 11 Jorge Manuel B. S. Vicetto (RETIRED) Gentoo Infrastructure gentoo-dev 2009-03-07 16:54:54 UTC
It seems the latest versions have fixed the memory issues.
If anyone still suffers from the memory issues, please reopen this bug.