Ok I just had the issue happen again (well when it happens in a way that can't
be recovered by closing down open windows)
Basically there are some very odd graphics alignment glitches ctrl + shift +
f12 and back again does fix the issue.
I'm not getting anything random like memory issues and I cheked the ram a
while back. This may be a a different problem than the one I get with the too
many windows open which prevents me from, for instance, running video in full
screen at anything more than stop motion type speeds.
The glitches happen in other things than the task manager, sometimes the odd
icon will get funny in the system tray and the shutdown / logout dialogue has
some alignment issues.
The task manager isses are odd though, I can click on the swatches and they
work find where they are, it's a bit like half of them anchor left and half
anchor to the right hand side (so they overlap) and there's more on each line
then can fit
I've tried changing all the various themesto glass or oxygen or qtcurve or
variants off etc..
I'm going to upload some screen shots and bits to the internet but for now:
On Saturday 08 Jan 2011 00:16:40 Thomas Lübking wrote:
> Am Friday 07 January 2011 schrieb oliverthered:
> > I'm getting an issue what appears to be GPU memory issues, specifically
> > the memory seems to be getting eaten up quite quickly even though I've
> > got loads of system ram and not a huge number of application windows or
> > apps running. I belive my graphics card has 512MB or ram or maybe 1GB
> > but it's a GeForce 7900 GS.
>
> "nvidia" or "nouveau"?
> nvidia
>
> > I've changed over to none oxygen version of everything (as that was
> > pointed to as the culprit for some leakyness), but closing down windows
> > seems to free up the ram and I can run things like projectM full screen
> > again and with no performance issues.
>
> Can you actually confirm that the RAM hunger is distributed evenly among
> your running applications ("top") and not everything is just sucked by
> only one (X11?) process?
Ok xorg was using a lot of ram
mem shared
Xorg 729248k 9060
virtuoso-t 505896 6600
kwin 144104 40804
amarok 131496 22564
plasma-desktop 80912 30958
chrome 63856 24612
knotify4 59168 15160
and a load more
>
> Usually graphical stuff (including and good god esp. opengl) ends up in
> your VRAM (ie. on the GPU), you can query the used X11 resources by
> "xrestop"
>
Here's the top few from xrestop
xrestop - Display: :0
Monitoring 76 clients. XErrors: 0
Pixmaps: 307889K total, Other: 343K total, All: 308233K total
res-base Wins GCs Fnts Pxms Misc Pxm mem Other Total PID Identifier
1600000 103 1 0 1035 1966 197975K 48K 198024K 1257 kwin
1a00000 126 93 0 4244 4644 66357K 113K 66471K 1463 plasma-
desktop
7c00000 44 15 0 549 862 14015K 21K 14036K 3975 From Camera
�...@~s Dolphin
8800000 47 39 1 37 55 4968K 4K 4972K 6158 Getting
Started.pdf - Adobe Reader
5400000 20 5 0 151 301 4215K 7K 4223K 1992 fault
finding/identification (pre-debugging?), a check to see if something
7600000 8 3 0 1858 1908 3794K 44K 3839K 15616 oliverthered
- Skype�~D� (Beta)
7200000 39 2 0 68 135 3481K 4K 3485K 8962 vodaphone
voucher details �...@~s Kate
6200000 35 11 0 240 375 3009K 9K 3019K 5062 Kopete
5800000 10 50 1 17 47 2104K 3K 2107K 5008 Google -
Google Chrome
5600000 6 4 0 23 82 1984K 2K 1986K 2005 KDE
Grahphics glickes : xrestop
> in doubt: ask your distro whether they run anything (everything...) by
> "--graphicssystem raster" and then tell them to stop doing this ;-)
>
cd /proc
sudo grep -R --include='cmdline' --exclude-dir='[a-z]*' '.*graphicssystem.*' *
returned no results (checked grep command by putting kde in the match
exprssion and stuff got returned matching kde in the commandline)
> > I would have expected that opengl should put stuff into system memory as
> > it's ment to do it's own memory mangement, at least for some stff etc...
>
> yes, as last resort - but your GPU can carry some windows before mapping to
> sysram.
> please notice that ARGB enabled windows will take 33% more memory than
> "ordinary" ones. konsole and most plasma-desktop windows use ARGB and we
> recently figured that apparently gdk driven GL clients (like at least eg.
> cairo-dock) will make all Qt clients (or rather everything?) use ARGB
> drawables
>
> the nvidia driver has however it's very own pitfall.
> call "nvidia-settgins -a PixmapCache=0; nvidia-settgins -a PixmapCache=1"
> from time to time (every 30 minutes and right after your desktop is
> loaded) to improve performance...
>
ok, I may put that in a cron job and in a .rc file then.
Would it be worth just doing it when the system load if more idle i.e. is it
better that it happens when nothing is happening or is it better that it's run
when lots is happening. I realise that the desktop will be getting rendered
all the time, but I'm not sure how you deal with dirtywindows and the like (I
would assume an attempt at doing as little as possible if nothing is happening
in the window, but I not familiar with the inner workings of X beyond it is
capable of network transparancy but I seem to remember VNC not liking it too
much because of dirtyness problems (though that may have been microsoft
windows)
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
