I'm having the same problem in Ubuntu 9.04 with intel GMA950 graphics. I
use intel drivers from xorg-edgers PPA. i am still not sure if it is
compiz bug or a intel driver bug or something else. All I know is that
after a few hours or mostly a day of usage of my system, the swap drive
is getting
This bug is gone in Intrepid. I am running with version 177 of the
nvidia driver and my compiz-real process rarely gets about 100MB. It
used to take about 3 hours to get to 400MB. No more lock-ups...I am
completely thrilled. I have a GE Force Go 7400.
--
Memory leak in nvidia-glx-new's
This bug is still prevalent in 8.04.1 as of 2008-08-20; as the current
nvidia driver (169.12+2.6.24.13-19.45) sets a flag in the pages used to
map textures from, and the flag isn't cleared on the correct path,
allocated pages get locked. There is a (userspace) per-process 32KB
locked limit for
i think the nvidia-driver should be also updated for users that don't
use envy-ng. This is a quite critical bug that can lead to data-loss.
for example the kernel killed once my virtualbox-session cause there
wasn't any free memory left ...
--
Memory leak in nvidia-glx-new's
ccc1, Graeme: the driver will be available through envyng ASAP.
--
Memory leak in nvidia-glx-new's GL_EXT_texture_from_pixmap
https://bugs.launchpad.net/bugs/151168
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
That's what I figured. Thanks again for all your hard work on the envy
project, Alberto. It really makes things a lot less painful for us
NVidia users. :)
--
Memory leak in nvidia-glx-new's GL_EXT_texture_from_pixmap
https://bugs.launchpad.net/bugs/151168
You received this bug notification
any chance getting the just released stable nvidia driver 173.14.12 via
a hardyupdate or do we have to wait till 8.10?
--
Memory leak in nvidia-glx-new's GL_EXT_texture_from_pixmap
https://bugs.launchpad.net/bugs/151168
You received this bug notification because you are a member of Ubuntu
Bugs,
I suspect it won't be in hardy-updates, but that it will be available
via envy-ng. Confirm with the envy project, however.
--
Memory leak in nvidia-glx-new's GL_EXT_texture_from_pixmap
https://bugs.launchpad.net/bugs/151168
You received this bug notification because you are a member of Ubuntu
Can you enable the hardy-proposed and hardy-updates repositories,
install EnvyNG so as to install the latest release of the driver?
In any case this is definitely a bug which we can't fix. NVIDIA should
deal with it.
** Changed in: linux-restricted-modules-2.6.24 (Ubuntu)
Status:
to avoid any confusion, the memory leak has been fixed since:
nvidia beta drivers 173.08
--
Memory leak in nvidia-glx-new's GL_EXT_texture_from_pixmap
https://bugs.launchpad.net/bugs/151168
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
173.14 has been released by nVidia
http://www.nvnews.net/vbulletin/showthread.php?t=113919
No mentioned of having fixed a memory leak. Anyone know when it will
show up in the repos anywhere?
--
Memory leak in nvidia-glx-new's GL_EXT_texture_from_pixmap
https://bugs.launchpad.net/bugs/151168
Too bad 173.08 is a beta driver, and EnvyNG's author clearly states that
he would only include stable driver in EnvyNG. I hope Nvidia will soon
release their new stable driver, 169.12 not only has this memory leak
problem but also couldn't detect the correct EDID information on certain
laptops (my
memory leak confirmed when i am closing windows with enabled compiz
nvidia-glx-new
--
Memory leak in nvidia-glx-new's GL_EXT_texture_from_pixmap
https://bugs.launchpad.net/bugs/151168
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Any chance of getting this driver in Hardy, or is it too beta and too
close to Hardy release?
--
Memory leak in nvidia-glx-new's GL_EXT_texture_from_pixmap
https://bugs.launchpad.net/bugs/151168
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Unlikely to get into Hardy simply because it is a beta driver.
However, with envyng in hardy, it makes it pretty painless for users to
upgrade to it.
--
Memory leak in nvidia-glx-new's GL_EXT_texture_from_pixmap
https://bugs.launchpad.net/bugs/151168
You received this bug notification because
I confirm, the new beta driver 173.08 on Hardy (2.6.24-16-generic) solve
the memory leak problem!!!
Before installing I used the klerfayt's procedure:
sudo apt-get remove --purge nvidia-kernel-common
sudo apt-get install libc6-dev pkg-config xserver-xorg-dev
sudo /etc/init.d/kdm stop or sudo
thanks for the notice urys!
Confirmed:
nvidia beta drivers 173.08 do not leak memory in Kubuntu 7.10 with geforce go
6200 turbocache 128MB graphics card
here is what you need to do in gutsy before you run nvidia beta drivers
installer:
sudo apt-get remove --purge nvidia-kernel-common
sudo
Kernel 2.6.24-15 and 2.26.24-15
--
Memory leak in nvidia-glx-new's GL_EXT_texture_from_pixmap
https://bugs.launchpad.net/bugs/151168
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I was installed new Beta 173.08 yeasterday on HH 8.04. NO MEMORY LEAKS
NOW!
--
Memory leak in nvidia-glx-new's GL_EXT_texture_from_pixmap
https://bugs.launchpad.net/bugs/151168
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
just to confirm Daniel Lombraña observation, the changed option
INDIRECT=no to yes in /usr/bin/compiz worked for me too (gutsy,
169.12 w/ twinview on a NVS-285)
--
Memory leak in nvidia-glx-new's GL_EXT_texture_from_pixmap
https://bugs.launchpad.net/bugs/151168
You received this bug
yeah they can't reproduce it cause they are using cards with too much
memory. As someone wrote somewhere this problems disappears if one has
enough videomemory. So instead of sending nvidia hardware, they should
test with a mainboard with integrated nvidia graphics set videomemory to
32MB. Then
Confirmed on Hardy with 171.06
--
Memory leak in nvidia-glx-new's GL_EXT_texture_from_pixmap
https://bugs.launchpad.net/bugs/151168
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
If you want this bug fixed then send the affected hardware to nvidia
corporation. They have issues reproducing the memory leak with hardware
available to them ... by their own words.
--
Memory leak in nvidia-glx-new's GL_EXT_texture_from_pixmap
https://bugs.launchpad.net/bugs/151168
You received
i strongly suggest all users experiencing this problem to voice their
concern to nvidia, rather than to ubuntu.
nvnews is a great place for this, as nvidia staff monitor it. Several
nvidia staff have already replied to an ongoing thread, but have not
been able to reproduce the problem. If we
I have the same problem, I have Ubuntu Gutsy the Gibbon with a nvidia
GeForce Go 7400 card and using nvidia-glx-new from the repositories. I
have modified the compiz script from /usr/bin/ and changed the option
INDIRECT=no to yes, and now compiz.real is always at 19.7 MB while
without this option
Confirmed on Hardy with 169.09.
** Changed in: linux-restricted-modules-2.6.24 (Ubuntu)
Sourcepackagename: linux-restricted-modules-2.6.22 =
linux-restricted-modules-2.6.24
Importance: Undecided = High
Status: New = Confirmed
--
Memory leak in nvidia-glx-new's
This may be fixed...but it hasn't made it into general updates yet...
http://www.nvidia.com/object/linux_display_x86_96.43.05.html
At least it's on the radar,
cs
--
Memory leak in nvidia-glx-new's GL_EXT_texture_from_pixmap
https://bugs.launchpad.net/bugs/151168
You received this bug
No, that fix means that new windows are not empty anymore. This bug is
about compiz memory consumption growing until you have to kill it. That
package is in Hardy already.
--
Memory leak in nvidia-glx-new's GL_EXT_texture_from_pixmap
https://bugs.launchpad.net/bugs/151168
You received this bug
Hi,
just wanted to confirm that the workaround posted by evilspy (increasing
the memory in the BIOS) worked fine for me.
Andreas
--
Memory leak in nvidia-glx-new's GL_EXT_texture_from_pixmap
https://bugs.launchpad.net/bugs/151168
You received this bug notification because you are a member of
I don't read all. Sorry my english. I'm spanish. I had this problem, but
I had reading this forum. I uninstall the package emerald. I don't have
this problem!! All right!! :D.
Try this solutions, I wait all right for all ;). Bye!
--
Memory leak in nvidia-glx-new's GL_EXT_texture_from_pixmap
Sorry, I see top now, and it isn't true. I have the problem :S. Hop.
--
Memory leak in nvidia-glx-new's GL_EXT_texture_from_pixmap
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.
--
I'm not sure if I'm having the same issue, but I am experiencing some
severe memory issues. After a reboot, free -m looks like this:
[EMAIL PROTECTED]:~$ free -m
total used free sharedbuffers cached
Mem: 3033724 2309 0
Nice to see that others have the same problems as me. (roughly speaking
:P)
Linux straylight 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007
i686 GNU/Linux
Intel Centrino 1.8Ghz, 1GB RAM, nVidia Geforce Go 6200.
After a random amount of time, everything slows down, making it
completely
$ cat /proc/5654/status
Name: compiz.real
State: S (sleeping)
SleepAVG: 98%
Tgid: 5654
Pid:5654
PPid: 5547
TracerPid: 0
Uid:1842184218421842
Gid:100 100 100 100
FDSize: 64
Groups: 4 20 24 25 29 30 44 46 100 104 108 109 110 115 117 201 903
I'm still seeing this issue under 169.04. Over on the NV forum, the
developers are pretty surprised to hear others are seeing it too. I
think the issue is in the animations plugin. Just turning it on and off
causes memory usage to start increasing. I'm leaving it off for now to
see how things run
Replies on that thread seem to indicate there's a newer driver and it's
still broken, so I guess we can't expect any fix right away?
--
Memory leak in nvidia-glx-new's GL_EXT_texture_from_pixmap
https://bugs.launchpad.net/bugs/151168
You received this bug notification because you are a member of
I would expect it to be still broken if it isn't mentioned in driver
release notes ;-)
On Nov 20, 2007 8:57 PM, Graeme Humphries [EMAIL PROTECTED] wrote:
Replies on that thread seem to indicate there's a newer driver and it's
still broken, so I guess we can't expect any fix right away?
--
I would expect it to be still broken if it isn't mentioned in driver
release notes ;-)
I wouldn't. NVIDIA have inadvertantly fixed various bugs in past driver
releases.
--
Memory leak in nvidia-glx-new's GL_EXT_texture_from_pixmap
https://bugs.launchpad.net/bugs/151168
You received this bug
release notes:
http://www.nvidia.com/object/linux_display_ia32_169.04.html
On Nov 21, 2007 12:13 AM, Murat Güneş [EMAIL PROTECTED] wrote:
I would expect it to be still broken if it isn't mentioned in driver
release notes ;-)
I wouldn't. NVIDIA have inadvertantly fixed various bugs in past
According to Nvidia, it is a bug in the Nvidia driver and will be fixed in the
next release, whenever that is.
see: http://www.nvnews.net/vbulletin/showpost.php?p=1442530postcount=15
--
Memory leak in nvidia-glx-new's GL_EXT_texture_from_pixmap
https://bugs.launchpad.net/bugs/151168
You
I have try open many windows on my desktop with GeForce FX5600 (128mb)
and compiz there eats memory too. Drivers version are the same as on
laptop.
--
Memory leak in nvidia-glx-new's GL_EXT_texture_from_pixmap
https://bugs.launchpad.net/bugs/151168
You received this bug notification because you
Hi all,
I've switched to an Inspiron 1720 which has an 8600M GT chipset -
previously I had been using an Inspiron 8600 with a 64Mb GeForce 5200.
Compiz.real is behaving itself so I guess the problem is related to the
amount of video memory available. I'm using a release version of Gutsy
on
As Kaltsoplyn stated before, enabling indirect rendering gets rid of the
leaking !!!
I enabled it via the compiz-icon and the usage immediately shrunk back to only
25MB and it stays stable.
btw,
The leaking only happens on my dell latitude d620 , which has an nvidia card
with 128MB of video,
Yes, see my comment above:
https://bugs.edge.launchpad.net/ubuntu/+source/compiz-fusion-plugins-
main/+bug/151168/comments/72
Previously, when the card ran out of video memory for window textures,
you'd get all-black windows instead of the proper texture (the BWB).
Using --indirect-rendering made
Hello, new to launchpad and ubuntu in general, so bear with me if what I say is
completely silly
Anyway I experience the same bug (fresh Gutsy install / Toshiba laptop Nvidia
Go5200 with nvidia drivers)
I tried compiz --replace and well, it works some times but not always.
However I also tried
Confirm on Sony Vaio FS415 laptop (GeForce Go6400), leaks for 900+mb by some
hours.
Using nvidia-glx-new, tryed nvidia-glx but it fails while loading driver.
--
Memory leak in nvidia-glx-new's GL_EXT_texture_from_pixmap
https://bugs.launchpad.net/bugs/151168
You received this bug notification
by the way - what's the normal usage of ram for Compiz in the beginning?
Does it go straight to 60MB or stays around 16MB?
2007/10/30, kaltsoplyn [EMAIL PROTECTED]:
Hello, new to launchpad and ubuntu in general, so bear with me if what I
say is completely silly
Anyway I experience the same
@klerfayt: it began at around 35Mb and it climbed as time went by.
I never saw a number larger than ~100Mb but then again I never let it run long
enough without a compiz --replace or sth.
I only have 512Mb and a lot of things running, so when memory leaks my laptop
quickly becomes unusable.
--
it's just that then I installed Ubuntu on other machine I saw also only
16MB used at start and was surprised - because here it uses 60MB
immediately at start
--
Memory leak in nvidia-glx-new's GL_EXT_texture_from_pixmap
https://bugs.launchpad.net/bugs/151168
You received this bug notification
I guess that on the other machine there is no hardware graphics acceleration,
so --indirect-rendering is on by default.
hmmm or vice versa :)
or maybe one machine does not have an nvidia chip, and thus no nvidia driver,
which seems to be the weak link of the whole situation.
But anyhow 60Mb at
I can confirm that.
I have the same problem with nVidia drivers (G72M [Quadro NVS 110M/GeForce Go
7300] on my Dell Latitude D620). With my 1GB ram I run out of memory in about
15 minutes! If I swap Normal visual effects to None, memory usage will drop
dramatically (from 90% to 40%). But when I
As far as I can tell, you will see this bug on any nVidia card with the
nvidia-glx-new drivers, but only once you've exhausted the onboard
texture memory. So I need to open a *lot* of windows on my 512Mb card
before it starts leaking, but it still does. With 64mb of memory,
you'll hit the limit
Obviously this is only a solution if our BIOS has these settings.
On my HP laptop there's no such settings in the BIOS. In fact, the BIOS
has only 3 settings to change :(
Argh
--
Memory leak in nvidia-glx-new's GL_EXT_texture_from_pixmap
https://bugs.launchpad.net/bugs/151168
You received
I do apologize for frequent posting, but it looks like Evilspy's
solution is *REAL* (kudos to him). It's probably the simplest possible
workaround available right now (apart from eliminating compiz entirely).
At least, it works for me as well.
ASUS M2NPV-VM motherboard with NVidia GeForce 6150
I must agree with Ramesh...
My (and probably his) frustration comes from the fact that I installed
Gutsy in a standard way: no hacks, no dirty tricks, just a few clicks to
upgrade from Feisty, everything by the book. With a mainstream machine
and a mainstream graphics card I expected smooth
I can now confirm Mike's findings: frame buffer of 128Mb is good enough
for Firefox/Thunderbird/Pidgin/Terminal/Video type of computer usage
(plus a number of special effects). In two and a half hours of regular
work and playing, compiz memory usage increased from modest 38Mb to
41Mb.
A number of
You should ask this from nvidia company due to the closed source drivers; if
it helps then I got pci express geforce go 6200 turbocache card with 128MB
(16MB real, rest is taken from ram) and suffer memory leak also...
2007/10/26, cuby [EMAIL PROTECTED]:
I have a pci express card from nvidia
I have a pci express card from nvidia with more than 128MB and I still have
this problem.
Can anyone explain this?
--
Memory leak in nvidia-glx-new's GL_EXT_texture_from_pixmap
https://bugs.launchpad.net/bugs/151168
You received this bug notification because you are a member of Ubuntu
Bugs,
You are correct klerfayt.
You should ask this from nvidia company due to the closed source drivers; if
it helps then I got pci express geforce go 6200 turbocache card with 128MB
(16MB real, rest is taken from ram) and suffer memory leak also...
Another strange thing happened today.
The bug
About last post... Sorry.
The problem is still there, but somehow it's progression is slower.
I've been opening and closing programs like a mad for 20 minutes (to further
test) and the resident memory climbed to 155MB and the virtual to 190MB, from
several hundreds. I have 1GB.
The memory
Just my two cents:
With everything fully up-to-date, I can only say:
gutsy + nvidia-glx-new + compiz = total disaster
I have an ASUS M2NPV-VM motherboard with an integrated NVidia GeForce
6150GPU. I use the following compiz plugins: Cube, Expo, Rotate Cube,
Viewport Switcher, Animations, Water
I'm with Sasa on this.
This issue is *really* critical. Is this already known upstream?
Also, any ubuntu devs to comment, and confirm this bug?
So far, there are two soluctions wich work for me right now:
1. Don't use Compiz. You can do this by disabling it in the appearance applet.
2. Issue a
I just cannot believe that this bug is almost three weeks old without a
solution on the horizon?!
It affects mainstream PCs, all of them with Ubuntu flagship product.
Isn't it enough to treat this issue as critical ('blocker' being a more
appropriate word)?
If Gutsy had been my first expereince
How fast this bug is fixed depends entirely on the actions/will of nVidia
company -- to give you an example -- it took them more than a year to fix
black window bug :-)
On 10/25/07, Sasa Markovic [EMAIL PROTECTED] wrote:
I just cannot believe that this bug is almost three weeks old without a
Here are 3 possible workarounds:
1) Install the xserver-xgl package (sudo aptitude install xserver-xgl, will
expose bugs in Wine)
2) Install the nvidia-glx drivers, rather than the nvidia-glx-new drivers (sudo
aptitude install nvidia-glx, may have to remove the
How about disabling compiz by default on turbocache cards? (or this memory
leak is random?)
2007/10/25, Chris Halse Rogers [EMAIL PROTECTED]:
Here are 3 possible workarounds:
1) Install the xserver-xgl package (sudo aptitude install xserver-xgl,
will expose bugs in Wine)
2) Install the
Another workaround is to do compiz --restart when the memory use gets
extreme. Window positions are retained.
--
Memory leak in nvidia-glx-new's GL_EXT_texture_from_pixmap
https://bugs.launchpad.net/bugs/151168
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Murat, you probably mean compiz --replace? It does not work on my
machine, either (compiz restarts, but system freezes, I can hardly
reboot it). I can recommend Chris' third solution: turn off compiz
completely and wait for a proper nvidia driver.
--
Memory leak in nvidia-glx-new's
On Thu, 2007-10-25 at 09:09 +, Chris Halse Rogers wrote:
Here are 3 possible workarounds:
1) Install the xserver-xgl package (sudo aptitude install xserver-xgl, will
expose bugs in Wine)
2) Install the nvidia-glx drivers, rather than the nvidia-glx-new drivers
(sudo aptitude install
1) Install the xserver-xgl package (sudo aptitude install xserver-xgl,
will expose bugs in Wine)
That one works for me so far. No major memory leaks yet. I did not mess
with the existing nvidia driver and all seems to be fine.
--
Memory leak in nvidia-glx-new's GL_EXT_texture_from_pixmap
** Changed in: compiz (Ubuntu)
Status: New = Invalid
--
Memory leak in nvidia-glx-new's GL_EXT_texture_from_pixmap
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.
--
ubuntu-bugs
with xgl fonts loose subpixel hinting?
--
Memory leak in nvidia-glx-new's GL_EXT_texture_from_pixmap
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.
--
ubuntu-bugs mailing list
Sasa, I didn't mean compiz --replace; but compiz --restart doesn't
seem to be documented anywhere, although effectively what it does is no
different than compiz --gweobrjgo4f or just compiz; it just restarts
Compiz. My point is that restarting Compiz is an (obvious) workaround.
--
Memory leak in
On Thu, 2007-10-25 at 16:01 +, Murat Güneş wrote:
Sasa, I didn't mean compiz --replace; but compiz --restart doesn't
seem to be documented anywhere, although effectively what it does is no
different than compiz --gweobrjgo4f or just compiz; it just restarts
Compiz. My point is that
Matt, I fail to see how this is strictly NVIDIA's fault. Many of the
people who have commented on this bug (including myself) had working
Compiz setups in Feisty, and they have now regressed to an unusable
state in Gutsy.
I was running the exact same NVIDIA driver (100.14.19) in Feisty as I am
in
Does the Xgl X server *still* not support XKB? That was a blocker for me
in the past (plus a source of frustration - why the heck would you want
XKB in your regular X server but not Xgl?!).
I believe nvidia-glx-new *is* required for some cards, including (I
believe) my NVS 285 Quadro. I tried
I solved my massive memory leak (compiz.real 800MiB after few hours)
simply by increasing gpu memory from bios from 64mb to 256mb. I have
6100 integrated graphics.
This way I can keep compiz.real memory at less than 40MiB after full day
of working but I don't think the underlying bug but only
On Thu, 2007-10-25 at 17:26 +, Ramesh Dharan wrote:
Matt, I fail to see how this is strictly NVIDIA's fault. Many of the
people who have commented on this bug (including myself) had working
Compiz setups in Feisty, and they have now regressed to an unusable
state in Gutsy.
I was
compiz --use-copy has never worked with any official version of compiz
(either from upstream, or the Ubuntu repositories). The copy-mode-
rendering path was patched in to Trevino's compiz packages. If you were
using Trevino's packages in Feisty and using this option, then you
obviously won't see
Ahah!
That explains a lot.
Thanks, Chris. Now if only I could get Trevino's package to work in
Gutsy.
--
Memory leak in nvidia-glx-new's GL_EXT_texture_from_pixmap
https://bugs.launchpad.net/bugs/151168
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
Confirming that rolling back from nvidia-glx-new to nvidia-glx
eliminates the memory leak.
best,
jim
On 10/25/07, Chris Halse Rogers [EMAIL PROTECTED] wrote:
compiz --use-copy has never worked with any official version of compiz
(either from upstream, or the Ubuntu repositories). The
That seems to confirm a leak in GL_EXT_texture_from_pixmap. When
running Xgl, Compiz doesn't use the nVidia provided t_f_p, and instead
uses Mesa's copy.
I'm retitling the bug with a more appropriate name.
** Summary changed:
- memory leak with ring
+ Memory leak in nvidia-glx-new's
By monitoring '/proc/compiz.real-pid/maps' I noticed that leak seems
to source to leaking '/dev/nvidia0' mmaps.
--
Memory leak in nvidia-glx-new's GL_EXT_texture_from_pixmap
https://bugs.launchpad.net/bugs/151168
You received this bug notification because you are a member of Ubuntu
Bugs, which
83 matches
Mail list logo
