Version: X.Org X Server 1.11.3.902 (1.11.4 RC 2) Latest Git version of xf86-video-ati and 2 X Radeon HD3450 and 4 X Monitors. It was required to run the lastest git version of xf86-video-ati to stop X from segfaulting on any opengl applications in my configuration. After 24 hours of use X creeps up from 400MB Ram to 3GB of Ram every time and requires a restart to clear. My friend is running an identical setup as me with same versions of code but only 3 monitors and all in a row. He does not have the memory Leak at all (Or at least it is not obvious) I am not a valgrind expert but if someone could tell me how to generate a useful report then I am willing to try also any other information you might think to be useful. Xorg.conf as follows: Section "ServerLayout" Identifier "Layout" Option "Xinerama" "on" Option "Clone" "off" Screen 0 "left" 0 400 Screen 1 "middle" 1600 0 Screen 2 "right" 3280 400 Screen 3 "bottom" 1600 1200 EndSection Section "Device" Identifier "AMDx1-1" Driver "radeon" BusID "PCI:3:0:0" Option "ZaphodHeads" "DVI-3" Screen 0 EndSection Section "Device" Identifier "AMDx1-2" Driver "radeon" BusID "PCI:3:0:0" Option "ZaphodHeads" "DVI-2" Screen 1 EndSection Section "Device" Identifier "AMDx16-1" Driver "radeon" BusID "PCI:1:0:0" Option "ZaphodHeads" "DVI-0" Screen 0 EndSection Section "Device" Identifier "AMDx16-2" Driver "radeon" BusID "PCI:1:0:0" Option "ZaphodHeads" "DVI-1" Screen 1 EndSection Section "Screen" Identifier "left" Device "AMDx16-1" EndSection Section "Screen" Identifier "middle" Device "AMDx1-1" EndSection Section "Screen" Identifier "right" Device "AMDx16-2" EndSection Section "Screen" Identifier "bottom" Device "AMDx1-2" EndSection
After some more research: This happens with the Closed AND Open source ATI driver. It happens on ARCH and Gentoo and also with 1.11.4 version of X Server.
Can you please provide more information. Can you use valgrind to find the source of the leak?
No response. Closing.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.