[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: Kwin direct rendering disabled on ATI
From:       Thomas_Lübking <thomas.luebking () gmail ! com>
Date:       2011-03-31 14:25:16
Message-ID: op.vs7o0db59bmiid () localhost ! localdomain
[Download RAW message or body]

ftr:
kde-devel is not exactly a user helpdesk, rather open bug reports or head  
over to the kde user forum for general help.
also you should contact kwin@kde.org since you've trouble with a  
particular application (iff this was a developer thing ;-)

in short:
---------
the catalyst driver (fglrx) is broken ever since (just google...), dri  
support isn't (wasn't? - you didn't post your glxinfo) properly detected  
and in consequence glsl fails as well.
you should be able to enforce direct rensering by exporting  
"KWIN_DIRECT_GL=1"
If you can, you should use the Xorg driver. Seriously.

BUT: your issue sounds more like some leak (just indirect rendering has a  
little overhead but not time driven or on a "i see dead pixels" level -  
"dri != HW acceleration", it's just about "who talks to the GPU -  
application or X11")

Try to suspend/resume compositing (press SHIFT+Alt+F12 twice) - if it's  
getting better, inspect top and xrestop for memory usage.
also turn off all effect plugins (but NOT compositing) and see whether the  
issue remains.
There are still at least some known leaks and state invalidations (prone  
statements) in some effects (but it's getting better ;-)
It could as well be a leak in the driver.

<mantra>
DO NOT, NEVEREVER, USE QHash::operator[] UNLESS YOU REALLY KNOW WHAT  
YOU'RE DOING! ;-)
</mantra>

Cheers,
Thomas
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]