Announcement

Collapse
No announcement yet.

Compiz with FGLRX causes leaks

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • icek
    started a topic Compiz with FGLRX causes leaks

    Compiz with FGLRX causes leaks

    Hi, Im using fglrx driver with compiz enabled and I did notice huge memory consumption of memory. Even scroling page in firefox eats megabytes of ram. I minimize and maximize window and 10 MB of ram is gone...

  • monraaf
    replied
    Well, I'm using the OSS drivers with Compiz now (radeon ddx + r600 dri) and they don't exhibit this behavior at all.

    So I stand by my comment: The problem lies with fglrx. Technically this may not be a memory leak or even a bug though, because the memory does seem to get released even without glxinfo after a while (at least here it did after some quick testing). Nevertheless taking away a couple of hundred MB of RAM like that is IMO very anti-social behavior.

    Leave a comment:


  • monraaf
    replied
    I'll give it a try later with the OSS radeon and R600 dri driver.

    Leave a comment:


  • icek
    replied
    And I?m pretty sure it is not fglrx fault, I have found people with nvidia reporting the same problem... this is my script which I run after login

    Code:
    #!/bin/sh -e
    
    sleep 30
    
    alltray evolution --no-alltray &
    gnome-do & 
    pidgin &
    pino &
    
    while [ 1 ]
    do
    	glxinfo	
    	sleep 60
    done
    
    return 0

    Leave a comment:


  • monraaf
    replied
    I normally don't use Compiz, but I just gave it a try. Unbelievable fglrx eating memory away like crazy in 8 MB chunks! And indeed a simple glxinfo releases the memory. I'm sure this is fglrx at fault and not X. top nor xrestop show a user process growing in memory usage. cat /proc/slabinfo seems to indicate a lot of kmalloc-8192 objects being allocated (and released when running glxinfo).

    Leave a comment:


  • tux_mark_5
    replied
    You can use glxinfo too, so no popups

    Leave a comment:


  • icek
    replied
    :-) funny, I did the same thing... but its really annoying if you play movie and glxgears window pops up... I believe that this is bug in Xserver, so I hope this bug will be fixed in Lucid...

    Leave a comment:


  • tux_mark_5
    replied
    I'm using Mobility Radeon HD 4870 X2 and I can confirm, that memory goes up whenever I scroll anything (firefox, krusader, skype - you name it).

    However, the interesting thing, that running glxgears or glxinfo frees the consumed memory. So as a temporary workaround you can write a scipt to call glxinfo every 20 seconds and that should fix most of the problems.

    Leave a comment:


  • icek
    replied
    Ok, I have filed the bug report, number 1738. But I dont thing it is bug in ati driver... Can somebody try to run HTOP and see if memory consumption goes up?

    Edit : Launchpad bug
    Last edited by icek; 01-17-2010, 04:34 PM.

    Leave a comment:


  • bridgman
    replied
    No, not like wrong colours and tearing in Xv at all (assuming that by wrong colours you mean outputting with a 16:235 range for HDMI TVs rather than 0:255 range for computer displays). Both of those involve new functionality that needs to be added to the driver - sync-to-vblank and buffer-queue code to deal with Xv tearing, and switchable output range for the colours.

    If your reference to "wrong colours" is something different from the "washed out colours" caused by using a 16:235 output range please let us know.

    As I understand it the fglrx devs went with a 16:235 range in order to correctly drive HDMI-attached HDTVs (at the expense of under-driving computer displays), while the radeon devs expanded the range out to 0:255 in order to correctly drive computer displays (at the expense of over-driving HDTVs). Different design decisions, not a bug in either case. The ideal solution would be to add a facility to switch between 16:235 and 0:255 depending on the type of display being used.

    This is getting off topic though -- the original poster reported an issue which doesn't seem to be showing up on our development and test systems, or on your system for that matter. Filing a bug report, or updating the existing mostly empty one, would probably help in that case.
    Last edited by bridgman; 01-16-2010, 04:02 PM.

    Leave a comment:

Working...
X