Xorg uses way more ram now.

forlack · 2008-12-17 18:48:24

I hate the new xorg btw. Totally blew up my system, but thats not the point now. I got it working for the most part, but after a few days of uptime xorg's ram usage will go up. Right now it is at 350mb, which is a ton considering it never use to go this high. Any fixes or way to simply refresh xorg without rebooting.

thomasknowles · 2008-12-17 19:55:59

ctrl + alt + backspace kills X then startx or whatever your custom graphical UI script maybe.

Last edited by thomasknowles (2008-12-17 19:56:16)

seenxu · 2008-12-17 21:40:31

yeah, the same issue here, my pc had already up for 3 days, and X used 252mb ram. I will keep my pc not reboot and see if this figure will go up even higher...

ST.x · 2008-12-17 22:34:17

complain to xorg devs

forlack · 2008-12-18 00:56:25

Ya its anoying. I know how to kill X with control alt backspace, the problem is with that new policy kit update or whatever I dont have a logout anymore so if i do that gdm doesnt take me to the login screen and its caught in some loop. Anyone else have this issue? All of this started with that large update... I dont want to vent too much, but who cares for the newest and greatest packages if you have to fix everything after it updates.

I just restarted my comp and xorg is now at 60 megs or thereabouts. Any other ideas out there?

skottish · 2008-12-18 02:30:52

On my system, right after boot I'm around 80MB total memory. After some usage, it climbs to around 185MB, with about 60MB of that being memory that X reserves. It pretty much stays exactly there. My question for you is, is X reserving hundreds of megabytes of RAM, or is that the total with cached memory?

JGC · 2008-12-18 11:30:46

There's a difference between virtual memory and memory actually in use. When you use composite, X will leak memory it seems. This was even worse with 1.4.x.
I don't know if it's your compositing manager or X itself that leaks the memory, but be aware that when using compositing, your whole screen is double buffered: once to show what's on your screen, and once on a offscreen buffer that your compositing manager reads to know what it should render on your screen.

Dieter@be · 2008-12-18 12:30:38

Odd, my box is up for 3.5 hours, X is using 50MB. Emerald 20MB

Last edited by Dieter@be (2008-12-18 12:31:22)

forlack · 2008-12-23 07:50:34

Ya mine will be fine for about a day, but it slowly climbs. I am at 1day 11 hours and it is at about 100 megs. In a couple more days it will be at 200mb.

dav7 · 2008-12-23 08:26:52

Well, I needed to reboot my system recently and as soon as it was up again and I restarted X... wallpaper, gnome-settings-daemon, openbox, tint2 and urxvtd running caused X itself to gobble up 200MB+ RAM.

-dav7

forlack · 2008-12-23 10:45:10

I might have something on this, or maybe not. I was looking at high ram usage items and i noticed gnome-screensaver was taking up 20mb so i killed it and after that X went from 150 to 70mb as well. Someone else want to see if its related?? Plus I had to add some xml to get suspend back, but I still dont have logout...?? anyone?

Arch Linux

#1 2008-12-17 18:48:24

Xorg uses way more ram now.

#2 2008-12-17 19:55:59

Re: Xorg uses way more ram now.

#3 2008-12-17 21:40:31

Re: Xorg uses way more ram now.

#4 2008-12-17 22:34:17

Re: Xorg uses way more ram now.

#5 2008-12-18 00:56:25

Re: Xorg uses way more ram now.

#6 2008-12-18 02:30:52

Re: Xorg uses way more ram now.

#7 2008-12-18 11:30:46

Re: Xorg uses way more ram now.

#8 2008-12-18 12:30:38

Re: Xorg uses way more ram now.

#9 2008-12-23 07:50:34

Re: Xorg uses way more ram now.

#10 2008-12-23 08:26:52

Re: Xorg uses way more ram now.

#11 2008-12-23 10:45:10

Re: Xorg uses way more ram now.

Board footer