xorg-server memory leak

[Snowhog]

Re: xorg-server memory leak

[dibl]

Re: xorg-server memory leak

I let my desktop computer run overnight, just to see if anything suspicious happened. The CPU (both cores) was idling when I sat down this morning and woke it up.

dibl@lucid:~$ uname -a
Linux lucid 2.6.32-21-generic #32-Ubuntu SMP Fri Apr 16 08:09:38 UTC 2010 x86_64 GNU/Linux
dibl@lucid:~$ uptime
 10:34:44 up 17:09, 1 user, load average: 0.50, 0.46, 0.43
dibl@lucid:~$ free
       total    used    free   shared  buffers   cached
Mem:    4056312  2906020  1150292     0   107832  1967664
-/+ buffers/cache:   830524  3225788
Swap:   2096472   17712  2078760

Except for being slightly surprised that it even touched swap that little bit, it looks fine to me.

[vinnywright]

Re: xorg-server memory leak

now I'm geting comfused..........allright that's normall ....... ..........

but the bytes are way up

vinny@desktop:~$ grep "object bytes" /sys/kernel/debug/dri/0/gem_objects
1884966912 object bytes
vinny@desktop:~$ grep "object bytes" /sys/kernel/debug/dri/0/gem_objects
2053820416 object bytes
vinny@desktop:~$

but no notesable performance hit ??

vinny@desktop:~$ uptime
11:48:08 up 2 days, 13:49, 1 user, load average: 0.88, 0.77, 0.57
vinny@desktop:~$ free
total used free shared buffers cached
Mem: 2028556 1953136 75420 0 182972 1233364
-/+ buffers/cache: 536800 1491756
Swap: 1108444 395016 713428
vinny@desktop:~$

and the kid's wear playing Alien Arena for howers last night...........I would have thought that mite have run it to a freez but no.

VINNY

[ccnjim]

Re: xorg-server memory leak

When I tried to fix the Kubuntu screen. (http://kubuntuforums.net/forums/inde...opic=3110848.0)
After $ sudo update-grub I get 3 memory leak messages in the terminal. Are these related to the memory leak problems being discussed here?

jim@krash:~$ sudo update-grub
[sudo] password for jim: 
Generating grub.cfg ...
Found linux image: /boot/vmlinuz-2.6.32-21-generic
Found initrd image: /boot/initrd.img-2.6.32-21-generic
Found linux image: /boot/vmlinuz-2.6.32-19-generic
Found initrd image: /boot/initrd.img-2.6.32-19-generic
Found memtest86+ image: /boot/memtest86+.bin
Found Windows 7 (loader) on /dev/mapper/isw_eccibegcgb_xp1
You have a memory leak (not released memory pool):
 [0xd0d200]
You have a memory leak (not released memory pool):
 [0x7c8200]
You have a memory leak (not released memory pool):
 [0x17bb6b0]
done
jim@krash:~$

Using this command I get:

grep "object bytes" /sys/kernel/debug/dri/0/gem_objects
 grep: /sys/kernel/debug/dri/0/gem_objects: No such file or directory

[Fintan]

Re: xorg-server memory leak

Using this command I get:

grep "object bytes" /sys/kernel/debug/dri/0/gem_objects
 grep: /sys/kernel/debug/dri/0/gem_objects: No such file or directory

Quote from here:
http://permalink.gmane.org/gmane.lin...tu.devel/30741

> Does this affect all hardware or only some hardware? When I try to
> reproduce the bug with
> for t in `seq 1 10`; do eog /usr/share/backgrounds ; echo `grep
> "object bytes" /sys/kernel/debug/dri/0/gem_objects` `ps ocomm,vsz,rss
> 1020|grep X`; done
> I get
> grep: /sys/kernel/debug/dri/0/gem_objects: No such file or directory

It affects only certain video drivers. For instance, -nvidia carries
its own GLX implementation and thus is unaffected.

[ccnjim]

Re: xorg-server memory leak

Quote from here:
http://permalink.gmane.org/gmane.lin...tu.devel/30741

Thanks for the link. I read that NVIDIA cards aren't affected. Does that mean my memory leaks are coming from somewhere else? Is there a way to trace them?

[Fintan]

Re: xorg-server memory leak

I am not expert with grub and tracing memory leaks.

I would suggest you start a new thread to that end. Don't forget to give your machine specs.

Hope that helps and good luck

[ccnjim]

Re: xorg-server memory leak

I am not expert with grub and tracing memory leaks.

I would suggest you start a new thread to that end. Don't forget to give your machine specs.

Thanks!
I was thinking that maybe I should start a new thread. I'm going to install the RC instead and see what happens. I'm running beta 2 now.

[dibl]

Re: xorg-server memory leak

I read that NVIDIA cards aren't affected.

My interpretation is "Systems with Nvidia cards which are using the Nvidia driver aren't affected.

Does that mean my memory leaks are coming from somewhere else?

Are you using the Nouveau driver?

[abalone]

Re: xorg-server memory leak

I was affected. Xorg was using >600 MB with driver nvidia.

[dibl]

Re: xorg-server memory leak

"Using" is not "leaking".

Was your system leaking memory, or just using a lot? On my rig, with 4GB of memory, xorg is using 1.5%, which is about 60MB.

For comparison, plasma-desktop is using 4.3%, and firefox-bin is using 2.5%. So xorg is actually #3 on the list of memory users on my system, at the moment. I've got bigger users, like vmware-vmx, which is not running at the moment.

[abalone]

Re: xorg-server memory leak

Well, I don't see why it should've come to use over 600 MB (and keep going up) without something having gone wrong...? Since I've installed the fixed/rolled-back/de-patched Xorg, it stays under 90 MB... 57 right now.

[dibl]

Re: xorg-server memory leak

Well, it looks like there is something about the patched xorg that your 7950GT likes.

I have to say this, and I don't mean to make you feel bad about your graphics card, but I think I've seen more problems with the 7950, over the years, than any other card in the 7xxx or 8xxx series of GPUs. My first Nvidia card was a 7900GS, and it was a fine card and worked great until I got itchy for an upgrade to an 8800. So it's now in my grandson's computer. But whatever they did with the 7950, it was a cause of far more problems getting the proprietary drivers working correctly.

But anyways if you're happy with the patched xorg then it looks like "problem solved".

[abalone]

Re: xorg-server memory leak

Unfortunately, the 7950 GT seems to be the best Nvidia card available for AGP systems... (now if only I could boot into a "pretty" console without X flunking out into "out of memory" panics every other time)

[ccnjim]

Re: xorg-server memory leak

I read that NVIDIA cards aren't affected.

My interpretation is "Systems with Nvidia cards which are using the Nvidia driver aren't affected.

Does that mean my memory leaks are coming from somewhere else?

Are you using the Nouveau driver?

First I'll post my copy of your query for memory usage so I don't have to start a new thread...yet

 jim@krash:~$ uname -a
Linux krash 2.6.32-21-generic #32-Ubuntu SMP Fri Apr 16 08:09:38 UTC 2010 x86_64 GNU/Linux
jim@krash:~$ uptime
 23:03:35 up 1:35, 1 user, load average: 1.00, 0.78, 0.62
jim@krash:~$ free
       total    used    free   shared  buffers   cached
Mem:    8193928  2139052  6054876     0   96168  1322368
-/+ buffers/cache:   720516  7473412
Swap:   11717624     0  11717624
jim@krash:~$

Are you using the Nouveau driver?

I don't think so.
I just installed the Lucid RC and used your guide for the nvidia drivers. This was the first time I was able to install/compile in Lucid with your guide.
Hardware drivers shows nvidia_current/driver is not activated.
I have all the candy, and am able to O.C. my 9800GTX+.
In Synaptic under nouveau it does show libdrm-nouveau1 as being installed. But nothing else.

Even in the RC when I follow the steps to change the low graphics mode screen at "update grub" I still get the memory leak message.

jim@krash:~$ sudo update-grub
[sudo] password for jim: 
Generating grub.cfg ...
Found linux image: /boot/vmlinuz-2.6.32-21-generic
Found initrd image: /boot/initrd.img-2.6.32-21-generic
Found memtest86+ image: /boot/memtest86+.bin
Found Windows 7 (loader) on /dev/mapper/isw_eccibegcgb_xp1
You have a memory leak (not released memory pool):
 [0x9de200]
You have a memory leak (not released memory pool):
 [0xf34200]
You have a memory leak (not released memory pool):
 [0x9919c0]
done
jim@krash:~$

The first time I saw it was in Lucid beta 1. So I ran memtest for 9+hrs. with no errors.

Is there a command I can run to confirm my graphics drivers? and trace my memory leaks?
I do apologize if this post has no relevance to the memory leak problem that this thread discusses.