Bug#457957: xserver-xorg: X server eats too much memory
Stefanos Harhalakis wrote: Apart from that, I believe that 1.5GB for X server a serious problem when caused by firefox when visiting google maps. Just go to google maps and watch the X server memory increasing by each move you do. It takes just a few minutes to exhaust system memory. Should I fill this bug report against firefox/iceweasel instead ? The reason is that Firefox asks the server to create tons of pixmap to store some images, textures, ... So maybe firefox is asking too much, but the server should be able to refuse at some point and maybe even drop some old pixmaps (not sure what it is supposed to do exactly these days). Anyway, there are some memory leak fixed in the upcoming Xserver 1.4.1, we'll see what happens soon. Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#457957: xserver-xorg: X server eats too much memory
On Thu, Dec 27, 2007 at 16:47:33 +0200, Stefanos Harhalakis wrote: X server eats a *lot* of memory. Currently it has a VMsize of 3GB with RSS 1.5GB. ps output: USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND root 6421 2.6 58.2 3083584 1210180 tty7 SLs+ 11:41 7:49 /usr/bin/X -br -nolisten tcp :0 vt7 -auth /var/run/xauth/A:0-NfXjOZ I believe that this is reproducable by openning firefox (or konqueror) and visiting google maps for some time. If that memory gets freed when you kill the firefox process, then it's not an X server bug. Cheers, Julien -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#457957: xserver-xorg: X server eats too much memory
On Friday 28 December 2007, Julien Cristau wrote: On Thu, Dec 27, 2007 at 16:47:33 +0200, Stefanos Harhalakis wrote: X server eats a *lot* of memory. Currently it has a VMsize of 3GB with RSS 1.5GB. ps output: USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND root 6421 2.6 58.2 3083584 1210180 tty7 SLs+ 11:41 7:49 /usr/bin/X -br -nolisten tcp :0 vt7 -auth /var/run/xauth/A:0-NfXjOZ I believe that this is reproducable by openning firefox (or konqueror) and visiting google maps for some time. If that memory gets freed when you kill the firefox process, then it's not an X server bug. Firefox was not running (it died). When X server had 1.5GB of memory, firefox/iceweasel was not running. Perhaps you should ignore this report until it happens again and I have more details using xrestop. Apart from that, I believe that 1.5GB for X server a serious problem when caused by firefox when visiting google maps. Just go to google maps and watch the X server memory increasing by each move you do. It takes just a few minutes to exhaust system memory. Should I fill this bug report against firefox/iceweasel instead ? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#457957: xserver-xorg: X server eats too much memory
Package: xserver-xorg Version: 1:7.3+8 Severity: important X server eats a *lot* of memory. Currently it has a VMsize of 3GB with RSS 1.5GB. ps output: USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND root 6421 2.6 58.2 3083584 1210180 tty7 SLs+ 11:41 7:49 /usr/bin/X -br -nolisten tcp :0 vt7 -auth /var/run/xauth/A:0-NfXjOZ I believe that this is reproducable by openning firefox (or konqueror) and visiting google maps for some time. The correspoding /proc/XXX/status file: Name: Xorg .. mpla mpla mpla... VmPeak: 3134804 kB VmSize: 3083584 kB VmLck: 168 kB VmHWM: 1537284 kB VmRSS: 1407900 kB VmData: 3062884 kB VmStk:84 kB VmExe: 1592 kB VmLib: 16420 kB VmPTE: 3056 kB System has 2GB of memory, it is currently using swap: # free total used free sharedbuffers cached Mem: 20759922023532 52460 0104 433200 -/+ buffers/cache:1590228 485764 Swap: 1171113618838489827288 System uptime is 5hours but this happened in about half an hour, so it is a fast memory leak (or whatever). -- Package-specific info: Contents of /var/lib/x11/X.roster: xserver-xorg /var/lib/x11/X.md5sum does not exist. X server symlink status: lrwxrwxrwx 1 root root 13 2007-02-02 21:21 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 1672764 2007-12-22 02:43 /usr/bin/Xorg Contents of /var/lib/x11/xorg.conf.roster: xserver-xorg VGA-compatible devices on PCI bus: 05:00.0 VGA compatible controller: nVidia Corporation NV43 [GeForce 6600] (rev a2) /etc/X11/xorg.conf does not match checksum in /var/lib/x11/xorg.conf.md5sum. Xorg X server configuration file status: -rw-r--r-- 1 root root 6261 2007-12-07 18:00 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: # nvidia-xconfig: X configuration file generated by nvidia-xconfig # nvidia-xconfig: version 1.0 ([EMAIL PROTECTED]) Tue Aug 1 21:11:12 PDT 2006 # /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 command: # sudo dpkg-reconfigure -phigh xserver-xorg Section InputDevice Identifier stylus Driver wacom Option Protocol ImPS/2 Option Device /dev/input/wacom Option Type stylus Option Threshold 10 Option Mode Relative Option USB On EndSection Section InputDevice Identifier eraser Driver wacom Option Protocol ImPS/2 Option Device /dev/input/wacom Option Type eraser Option USB On EndSection Section InputDevice Identifier cursor Driver wacom Option Protocol ImPS/2 Option Device /dev/input/wacom Option Type cursor Option USB On # Option Button2 BUTTON 3 #Option Button3 BUTTON 2 EndSection Section ServerLayout InputDevice stylusSendCoreEvents InputDevice eraserSendCoreEvents InputDevice cursorSendCoreEvents Identifier Default Layout Screen Default Screen 0 0 InputDeviceGeneric Keyboard #InputDeviceConfigured Mouse InputDeviceMS Mouse SendCoreEvents InputDeviceTrackball SendCoreEvents Option AIGLX on EndSection Section Files # path to defoma fonts FontPath/usr/share/fonts/X11/misc FontPath/usr/X11R6/lib/X11/fonts/misc FontPath/usr/share/fonts/X11/cyrillic FontPath/usr/X11R6/lib/X11/fonts/cyrillic FontPath/usr/share/fonts/X11/100dpi/:unscaled FontPath/usr/X11R6/lib/X11/fonts/100dpi/:unscaled FontPath/usr/share/fonts/X11/75dpi/:unscaled FontPath/usr/X11R6/lib/X11/fonts/75dpi/:unscaled FontPath/usr/share/fonts/X11/Type1 FontPath/usr/X11R6/lib/X11/fonts/Type1 FontPath/usr/share/fonts/X11/100dpi FontPath/usr/X11R6/lib/X11/fonts/100dpi FontPath/usr/share/fonts/X11/75dpi FontPath/usr/X11R6/lib/X11/fonts/75dpi FontPath/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType EndSection Section Module #Load i2c #Load bitmap #Load ddc Load extmod Load xtrap Load freetype Load glx Load
Bug#457957: xserver-xorg: X server eats too much memory
reassign 457957 xserver-xorg-core forcemerge 447526 457957 found 457957 2:1.4.1~git20071212-2 thank you Stefanos Harhalakis wrote: Package: xserver-xorg Version: 1:7.3+8 Severity: important X server eats a *lot* of memory. Currently it has a VMsize of 3GB with RSS 1.5GB. ps output: USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND root 6421 2.6 58.2 3083584 1210180 tty7 SLs+ 11:41 7:49 /usr/bin/X -br -nolisten tcp :0 vt7 -auth /var/run/xauth/A:0-NfXjOZ I believe that this is reproducable by openning firefox (or konqueror) and visiting google maps for some time. You should look at xrestop to find out who is allocating memory through the X server. I am merging with another similar bug. Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
