![]() |
|
|
#1 | |
|
Registered User
Join Date: Feb 2007
Posts: 5
|
hi folks,
anyone out there seeing a serious memory leak when running compiz or other compositing framework under the 100.14.19 driver and nvidia -glx-new? This has been a serious problem for a number of users of ubuntu gutsy; see the ubuntu bug report at https://bugs.launchpad.net/ubuntu/+s...in/+bug/151168 James at nvidia has helpfully written me to let me know that a bug report has been started at nvidia forh tis issue; I'm mostly writing to try to find out whether anyone is seeing this issue on platforms other than ubuntu. And if someone has a fix they use... thanks, matt |
|
|
|
|
|
|
#2 |
|
Registered User
Join Date: Feb 2007
Posts: 5
|
forgot to include the nvidia bug report log
|
|
|
|
| Sponsored Ads - Guests Only | |
|
|
|
|
#3 |
|
Registered User
Join Date: Oct 2007
Posts: 16
|
Same problem for me, running compiz with geforce go 6200 128mb.
It's totally unusable. Like written on the ubuntu bug report, I think it's a TFP related problem. |
|
|
|
|
|
#4 |
|
Registered User
Join Date: Oct 2007
Posts: 1
|
Same here
![]() Using a integrated Geforce Go 6150 with 128 shared memory on a HP Pavilion dv6106 Laptop. Hopefully Nvidia fixes this soon. Any comments from a Nvidia dev? |
|
|
|
|
|
#5 |
|
Registered User
Join Date: Sep 2005
Posts: 23
|
I can reproduce this with a Go6200 with 64MB of memory.
|
|
|
|
|
|
#6 |
|
NVIDIA Corporation
Join Date: Feb 2005
Location: San Jose
Posts: 36
|
As the original poster mentioned, we are aware of this issue and it is being debugged. No root cause or workarounds have been found yet. Could someone affected by this bug try the following experiment and report back: Does this get any better/worse if compiz is run with/without the --loose-binding option?
|
|
|
|
|
|
#7 | |
|
Registered User
Join Date: Mar 2007
Posts: 74
|
Quote:
I tried maximize/restore with single "ksysguard" window and didn't see any difference - both times memory usage (I was looking at "VMSize" tab) grow by 11MB |
|
|
|
|
|
|
#8 |
|
Registered User
Join Date: Jul 2006
Posts: 1
|
I tried running compiz both with and without --loose-binding, and in both cases see the same problem as described above. Minimizing and maximizing a window leads to an increase in Compiz memory usage of about 9MB each time I do it (but only if I have several windows open already).
|
|
|
|
|
|
#9 |
|
Registered User
Join Date: Oct 2007
Posts: 5
|
I have the same problem with Gutsy with driver 100.14.23 and GeForce Go 7400. Using loose-binding does not resolve the problem.
|
|
|
|
|
|
#10 |
|
NVIDIA Corporation
Join Date: Feb 2005
Location: San Jose
Posts: 36
|
OK, thanks for testing.
|
|
|
|
|
|
#11 |
|
Registered User
Join Date: Oct 2007
Posts: 4
|
Hi,
Only to answer to the question about other platforms I see no apparent memory leak bug. It would be possible that a slowness on restore, maximize, resize could be associated to this bug? This is the only difference I see with my brand new compiz-fusion compared with the an old beryl running on a Intel videocard. My system: Open SuSE10.3 x86_64 4GB Ram Geforce 8600M GT compiz-0.6.2-2.1 Driver: 100.14.19 BTW: is thera a 100.14.23 driver? Hope this to be helpful.
__________________
ASUS G1S-A1 4GB RAM, 8600M GT |
|
|
|
|
|
#12 |
|
Registered User
Join Date: Oct 2007
Posts: 5
|
100.14.23 ..since I am using Gutsy I used a Debian package that pulled the driver from nvidia site: http://albertomilone.com/nvidia_scripts1.html
Using indirect-rendering mitigates the leak problem, but I don't know if this ideal. |
|
|
|
![]() |
| Most Popular NVIDIA Based Graphics Cards | |
|
|
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
| Thread Tools | |
|
|