Bug#326956: xserver-xorg: Memory leak
On Thu, May 31, 2007 at 08:17:21PM +0200, Brice Goglin wrote: Hi, About 2 years ago, you reported (or replied to) a bug in the Debian BTS regarding a memory leak in the X server. Did any of you guys reproduce this problem recently? With Xorg/Etch? With latest xserver-xorg-core in unstable? If not, I will close this bug in the next weeks. Thanks, Brice I am currently using Ubuntu Feisty. This particular case of memory leaking does not occur now. Closing the bug sounds reasonable to me. -- Siep Kroonenberg -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#326956: xserver-xorg: Memory leak
On Thu, Sep 08, 2005 at 06:13:49PM +0200, David Mart?nez Moreno wrote: El miércoles, 7 de septiembre de 2005 19:27, Michel Dänzer escribió: Such behavior would be acceptable if X.org forgot old background images. But it doesn't. Try to successively load a series of background images, e.g. from the KDE wallpaper collection, and the memory occupied by Xorg will keep growing. First of all, verify using something like xrestop that it's not actually a client leaking references to the wallpaper pixmaps. Even if that's ruled out, freeing memory that was allocated from the heap can't always be returned to the system immediately because the heap can only shrink down to the highest allocation still in use. If that's the case, it should still be able to re-use a gap sometimes, especially when you switch to a smaller wallpaper, in which case the memory usage reported for the X server shouldn't increase. I'm curious as to which of these might apply to your situation, if any. Hello, Siep. I have been testing with xrestop and Michel is right. My machine runs KDE 3.4.2 and X.Org 6.8.2.dfsg.1-6, and I cannot see any increment in the memory usage in X. When I use a background, I see KDE Desktop process going up in the comsumption list, but it does not surpass 5917 KB in any case, even when I changed about twenty times my background desktop image. I even saw Xorg process in a common 'top' with 115 MB of resident memory. Another round of image switching did not changed Xorg's memory, until my default setting: no background image. In this moment, Xorg even give me back 5 MB of memory, falling to 110 MB. Is this true for you? If so, I would like to close this bug. Best regards, Ender. I believe there is still a memory leak. After startup, on my system Xorg takes up about 10mb of memory. This increases to 30mb and more after one or two days even after closing all applications. However, today memory use could no longer be increased without limit just by loading different background images: the memory sometimes goes up and sometimes down and doesn't go up further than about 3mb total amount. I don't know what caused the change. Now that I no longer have a simple way to trigger a memory leak you are probably right to close this bug. xserver-xorg is version 6.8.2.dfsg.1-5, and the window manager a hand-compiled fvwm 2.4.18. Regards, -- Siep Kroonenberg
Bug#326956: xserver-xorg: Memory leak
On Wed, Sep 07, 2005 at 11:57:01AM +0200, David Mart?nez Moreno wrote: El martes, 6 de septiembre de 2005 23:17, Siep Kroonenberg escribió: Loading a new background image on the root window usually increases the amount of memory taken up by Xorg by 2 or 3 mb, going by the RES column of top. I suppose that this is not a bug, but that X.Org is translating the image to a bitmap, thus growing itself in size. I made this test: I had this JPEG image: -rw--- 1 ender ender 132873 sep 7 11:49 orbes.jpg Then converted with Gimp to a bitmap, and: -rw-r--r-- 1 ender ender 2359350 sep 7 11:51 orbes.bmp -rw--- 1 ender ender 132873 sep 7 11:49 orbes.jpg It was a 1024x768 image. It resulted between 2 and 3 MB. Could anybody from debian-x confirm my suspicions that this is normal behavior before closing this bug? Best regards, Ender. Such behavior would be acceptable if X.org forgot old background images. But it doesn't. Try to successively load a series of background images, e.g. from the KDE wallpaper collection, and the memory occupied by Xorg will keep growing. -- Siep Kroonenberg
Bug#326956: xserver-xorg: Memory leak
Package: xserver-xorg Version: 6.8.2.dfsg.1-5 Severity: normal Loading a new background image on the root window usually increases the amount of memory taken up by Xorg by 2 or 3 mb, going by the RES column of top. -- Package-specific info: Contents of /var/lib/xfree86/X.roster: xserver-xfree86 xserver-xorg /etc/X11/X target unchanged from checksum in /var/lib/xfree86/X.md5sum. X server symlink status: lrwxrwxrwx 1 root root 17 Jul 24 22:21 /etc/X11/X - /usr/bin/X11/Xorg -rwxr-xr-x 1 root root 2167168 Aug 11 15:48 /usr/bin/X11/Xorg Contents of /var/lib/xfree86/xorg.conf.roster: xserver-xorg VGA-compatible devices on PCI bus: :00:10.0 VGA compatible controller: ATI Technologies Inc Rage Mobility M3 AGP 2x (rev 02) /var/lib/xfree86/xorg.conf.md5sum does not exist. Xorg X server configuration file status: -rw-r--r-- 1 root root 4028 Aug 11 13:34 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: # /etc/X11/xorg.conf (xorg X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the /etc/X11/xorg.conf manual page. # (Type man /etc/X11/xorg.conf at the shell prompt.) # # This file is automatically updated on xserver-xorg package upgrades *only* # if it has not been modified since the last upgrade of the xserver-xorg # package. # # If you have edited this file but would like it to be automatically updated # again, run the following commands: # # cp /etc/X11/xorg.conf /etc/X11/xorg.conf.custom # sudo sh -c 'md5sum /etc/X11/xorg.conf /var/lib/xfree86/xorg.conf.md5sum' # sudo dpkg-reconfigure xserver-xorg Section Files # FontPathunix/:7100# local font server # if the local font server has problems, we can fall back on these FontPath /usr/local/lib/fonts/win/:unscaled FontPath/usr/lib/X11/fonts/misc:unscaled # FontPath /usr/lib/X11/fonts/cyrillic FontPath/usr/lib/X11/fonts/75dpi/:unscaled FontPath/usr/lib/X11/fonts/100dpi/:unscaled #FontPath /usr/lib/X11/fonts/Type1 #FontPath /usr/lib/X11/fonts/CID FontPath/usr/local/lib/fonts/Type1 FontPath/usr/local/lib/fonts/math-ttf/cmtex-ttf FontPath/usr/local/lib/fonts/math-ttf/mathematica-ttf FontPath/usr/local/lib/fonts/TrueType FontPath/usr/local/lib/fonts/jre # FontPath/usr/lib/X11/fonts/cyrillic # FontPath/usr/lib/X11/fonts/100dpi # FontPath/usr/lib/X11/fonts/75dpi # paths to defoma fonts FontPath/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType FontPath/var/lib/defoma/x-ttcidfont-conf.d/dirs/CID EndSection Section Module LoadGLcore Loadbitmap Loaddbe Loadddc Loaddri Loadextmod Loadfreetype Loadglx Loadint10 Loadrecord Loadtype1 Loadvbe # Loadwacom EndSection Section InputDevice Identifier Generic Keyboard Driver keyboard Option CoreKeyboard Option XkbLayout us Option XkbRules xorg Option XkbModel macintosh EndSection # Option XkbRules xfree86 # Option XkbModel pc104 Section InputDevice Identifier Configured Mouse Driver mouse Option CorePointer Option Device/dev/input/mice Option Protocol ImPS/2 Option Emulate3Buttons true EndSection Section InputDevice Driver wacom Identifier WacomMouse Option Device /dev/wacom Option Mode Relative # Option Threshold 6 Option Type cursor Option USB on EndSection Section InputDevice Driver wacom Identifier Wacom Option Device /dev/wacom Option Mode Absolute # Option Threshold 6 Option Type stylus Option USB on EndSection Section Device Identifier ati Driver ati BusID PCI:0:16:0 Option UseFBDev true EndSection Section Monitor Identifier laptop Option DPMS HorizSync 30-57 VertRefresh 43-72 EndSection Section Screen Identifier Default Screen Device ati Monitor laptop DefaultDepth24 SubSection Display Depth 1 Modes 1024x768 EndSubSection SubSection Display Depth 4 Modes 1024x768 EndSubSection SubSection Display Depth 8
Bug#319895: xlibs: After upgrading to xserver-xorg, Ctrl-Alt-Fn for virtual consoles stopped working.
Package: xlibs
Version: 4.3.0.dfsg.1-14
Severity: normal
The problem might be that dpkg-reconfigure suggests xorg as rules
file, which isn't included in the package. Therre were also messages
of failure to load a keyboard map. After changing XkbRules to
xfree86 in xorg.conf, virtual consoles were once more available.
Anyhow, the diagnostics that follow refer to the current situation,
i.e. after this repair.
-- Package-specific info:
Keyboard-related contents of XFree86 X server log file
/var/log/XFree86.0.log:
(==) Using config file: /etc/X11/XF86Config-4
(==) ServerLayout Default Layout
(**) |--Screen Default Screen (0)
(**) | |--Monitor Generic Monitor
(**) | |--Device Matrox Graphics, Inc. MGA G400 AGP
(**) |--Input Device Generic Keyboard
(**) Option XkbRules xfree86
(**) XKB: rules: xfree86
(**) Option XkbModel pc104
(**) XKB: model: pc104
(**) Option XkbLayout us
(**) XKB: layout: us
(==) Keyboard: CustomKeycode disabled
(**) |--Input Device Configured Mouse
(**) |--Input Device Wacom
(**) |--Input Device WacomMouse
(WW) The directory /usr/lib/X11/fonts/CID does not exist.
Entry deleted from font path.
--
(==) MGA(0): Direct rendering enabled
(==) RandR enabled
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension LBX
(II) Initializing built-in extension XC-APPGROUP
(II) Initializing built-in extension SECURITY
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFree86-Bigfont
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
(II) Keyboard Generic Keyboard handled by legacy driver
(**) Option Protocol ImPS/2
(**) Configured Mouse: Protocol: ImPS/2
(**) Option CorePointer
(**) Configured Mouse: Core Pointer
(**) Option Device /dev/input/mouse0
XFree86 X server log files on system:
-rw-rw-r-- 1 root root 38143 Jul 25 11:01 /var/log/XFree86.0.log
Compiled XKB description for X server :0.0:
xkb_keymap {
xkb_keycodes xfree86+aliases(qwerty) {
minimum = 8;
maximum = 255;
ESC = 9;
AE01 = 10;
AE02 = 11;
AE03 = 12;
AE04 = 13;
AE05 = 14;
AE06 = 15;
AE07 = 16;
AE08 = 17;
AE09 = 18;
AE10 = 19;
AE11 = 20;
AE12 = 21;
BKSP = 22;
TAB = 23;
AD01 = 24;
AD02 = 25;
AD03 = 26;
AD04 = 27;
AD05 = 28;
AD06 = 29;
AD07 = 30;
AD08 = 31;
AD09 = 32;
AD10 = 33;
AD11 = 34;
AD12 = 35;
RTRN = 36;
LCTL = 37;
AC01 = 38;
AC02 = 39;
AC03 = 40;
AC04 = 41;
AC05 = 42;
AC06 = 43;
AC07 = 44;
AC08 = 45;
AC09 = 46;
AC10 = 47;
AC11 = 48;
TLDE = 49;
LFSH = 50;
BKSL = 51;
AB01 = 52;
AB02 = 53;
AB03 = 54;
AB04 = 55;
AB05 = 56;
AB06 = 57;
AB07 = 58;
AB08 = 59;
AB09 = 60;
AB10 = 61;
RTSH = 62;
KPMU = 63;
LALT = 64;
SPCE = 65;
CAPS = 66;
FK01 = 67;
FK02 = 68;
FK03 = 69;
FK04 = 70;
FK05 = 71;
FK06 = 72;
FK07 = 73;
FK08 = 74;
FK09 = 75;
FK10 = 76;
NMLK = 77;
SCLK = 78;
KP7 = 79;
KP8 = 80;
KP9 = 81;
KPSU = 82;
KP4 = 83;
KP5 = 84;
KP6 = 85;
KPAD = 86;
KP1 = 87;
KP2 = 88;
KP3 = 89;
KP0 = 90;
KPDL = 91;
SYRQ = 92;
MDSW = 93;
LSGT = 94;
FK11 = 95;
FK12 = 96;
HOME = 97;
UP = 98;
PGUP = 99;
LEFT = 100;
RGHT = 102;
END = 103;
DOWN = 104;
PGDN = 105;
INS = 106;
DELE = 107;
KPEN = 108;
RCTL = 109;
PAUS = 110;
PRSC = 111;
KPDV = 112;
RALT = 113;
BRK = 114;
LWIN = 115;
RWIN = 116;
MENU = 117;
FK13 = 118;
FK14 = 119;
FK15 = 120;
FK16 = 121;
FK17 = 122;
KPDC = 123;
LVL3 = 124;
ALT = 125;
KPEQ = 126;
SUPR = 127;
HYPR = 128;
XFER = 129;
I02 = 130;
NFER = 131;
I04 = 132;
AE13 = 133;
I06 = 134;
I07 = 135;
I08 = 136;
I09 = 137;
I0A = 138;
I0B = 139;
I0C = 140;
I0D = 141;
I0E = 142;
I0F = 143;
I10 = 144;
I11 = 145;
I12 = 146;
I13 = 147;
I14 = 148;
I15 = 149;
I16 = 150;
I17 = 151;
I18 = 152;
I19 = 153;
I1A = 154;
I1B = 155;
META = 156;
I1E = 158;
I1F = 159;
I20 = 160;
I21 = 161;
I22 = 162;
I23 = 163;
I24 = 164;
I25 = 165;
I26 = 166;
I27 = 167;
I28 = 168;
I29 = 169;
I2B = 171;
I2C = 172;
I2D = 173;
I2E = 174;
I2F = 175;
I30 = 176;
I31 = 177;
I32 = 178;
I33 = 179;
I34 = 180;
I39 = 185;
I3A = 186;
I3B = 187;
I3C = 188;
I42 = 194;
I43 = 195;
I44 = 196;
I45 = 197;
I4A = 202;
I54 = 212;
I55 = 213;
I56 = 214;
I57 = 215;
I58
