hmm very interest.. with glxgears i become this warning:
[EMAIL PROTECTED]:~$ glxgears *********************************WARN_ONCE********************************* File r300_mem.c function r300_mem_alloc line 225 Ran out of GART memory (for 1048576)! Please consider adjusting GARTSize option. *************************************************************************** 8014 frames in 5.0 seconds = 1602.617 FPS 8525 frames in 5.0 seconds = 1704.836 FPS 8508 frames in 5.0 seconds = 1701.421 FPS On 5/30/08, Michel Dänzer <[EMAIL PROTECTED]> wrote: > On Fri, 2008-05-30 at 11:01 +0200, Oliver Pinter wrote: >> I found the ground of the BUG (it think): >> >> many hundred of this line is in Xorg.log: >> >> enable montype: 1 > > No, that's just a harmless driver debugging message. > > If you really want to get to the bottom of this, first of all you should > rule out that it's a client leaking server resources. E.g., if you > restart all your clients (or at least the usual suspects such as > iceweasel), does the memory usage go back or at least stop growing for a > while? If so, it's probably a client issue. > > Otherwise, you'll have to try and find the leak with specialized tools > such as memprof or valgrind. > > Anything else just isn't very useful. > > > -- > Earthling Michel Dänzer | http://tungstengraphics.com > Libre software enthusiast | Debian, X and DRI developer > -- Thanks, Oliver -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]