From owner-freebsd-x11@FreeBSD.ORG Mon Jan 12 11:10:28 2004 Return-Path: Delivered-To: freebsd-x11@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 94E2916A4CE for ; Mon, 12 Jan 2004 11:10:28 -0800 (PST) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2D90D43DA1 for ; Mon, 12 Jan 2004 11:09:37 -0800 (PST) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.10/8.12.10) with ESMTP id i0CJ3aFR027750 for ; Mon, 12 Jan 2004 11:03:36 -0800 (PST) (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.12.10/8.12.10/Submit) id i0CJ3avx027744 for x11@freebsd.org; Mon, 12 Jan 2004 11:03:36 -0800 (PST) (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 12 Jan 2004 11:03:36 -0800 (PST) Message-Id: <200401121903.i0CJ3avx027744@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: x11@FreeBSD.org Subject: Current problem reports assigned to you X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Jan 2004 19:10:28 -0000 Current FreeBSD problem reports Critical problems Serious problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2001/11/19] ports/32121 x11 XFree86-4-Server: xf86cfg 4.1.0 writes ba o [2003/09/05] ports/56487 x11 Upgrading Xfree86-clients from ports over 2 problems total. Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2001/03/06] ports/25576 x11 XFree86-4 port installs manual pages with o [2002/10/18] ports/44252 x11 XFree86-4-Server port removes/overwrites s [2003/08/18] ports/55699 x11 [PATCH] making x11-servers/XFree86-4-Serv o [2003/09/01] ports/56275 x11 XFree86-4-Server: xf86config refers to no o [2003/11/14] ports/59297 x11 RADEON 7500 Warning message 5 problems total. From owner-freebsd-x11@FreeBSD.ORG Fri Jan 16 06:25:48 2004 Return-Path: Delivered-To: freebsd-x11@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A24B716A4CE; Fri, 16 Jan 2004 06:25:48 -0800 (PST) Received: from mail.mdacc.tmc.edu (mail.mdanderson.org [143.111.251.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id 58EB143D49; Fri, 16 Jan 2004 06:25:30 -0800 (PST) (envelope-from jonathan@fosburgh.org) Received: from ([143.111.64.231]) by mail.mdacc.tmc.edu (InterScan E-Mail VirusWall Unix); Fri, 16 Jan 2004 08:25:05 -0600 (CST) From: Jonathan Fosburgh To: freebsd-x11@freebsd.org Date: Fri, 16 Jan 2004 08:20:14 -0600 User-Agent: KMail/1.5.94 MIME-Version: 1.0 Content-Disposition: inline Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Message-Id: <200401160820.19794.jonathan@fosburgh.org> cc: freebsd-current@freebsd.org Subject: Possible memory leak in XFree86 X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Jan 2004 14:25:48 -0000 =2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I am cross-posting this to -current, since the problem is occuring in that= =20 environment. I first noticed this as far back as 5.0-RELEASE, but I had chalked it up to= =20 being hardware-related, for reasons I shall get into shortly. The problem= =20 has persisted throught XFree86 4.3.x (and through the most current snapshot= =20 available in the ports). I am also running KDE 3.x (3.1.x and now 3.2=20 BETA2). I am running -CURRENT (updated within the past couple of weeks) on= a=20 Pentium III-600mHz with 383MB (from dmesg) RAM. Originally, I had an nvidi= a=20 Riva TNT2 video card. For a brief time I used the nvidia drivers, but thos= e=20 were so unstable I never found out if this particular problem was=20 reproduceable with them. I now have an ATI Radeon 9200 and I see the same=20 things. =20 What is happening is that the X server slowly allocates more memory until a= ll=20 physical RAM and page space are allocated, and the pager starts killing off= =20 processes, eventually killing the X server. This seems to screw up syscons= =20 as well, and I wind up having to reboot to get my text consoles back. =20 Things have gotten slightly better of late, sometimes the memory is freed a= nd=20 the XFree86 process might go from say 400+MB (according to top) down to a=20 little less then 200MB, which appears to be normal for the Radeon using DRI= =2E =20 But this is not always the case. When I come in in the mornings I either=20 find my system very low on page space, or if I am gone for a couple of days= I=20 will generally find that X has been killed. I run screensavers and have DP= MS=20 set up to send the monitor to power-save mode. I have reduced my screensave= r=20 to just blanking the screen, but still to no avail. This morning, I came i= n=20 (after having been out yesterday) to find that X had been killed after=20 running out of page space. Now, here is why I initially thought it was hardware related (that is, in t= he=20 nvidia driver for XFree86): at home I have a Pentium III-600 with about the= =20 same amount of memory, running XFree86 4.3.x, KDE 3.1.x, screensavers, DPMS= ,=20 etc. The differences are that at home I have an SiS ViRGE video card=20 (incidentally, PCI versus AGP for work), and I am tracking -STABLE there. = =20 Only every once in awhile do I run out of page space at home, but my paging= =20 space is undersized there, whereas at work it is set to the recommended siz= e=20 from when I did the install, 753MB.=20 Where I am at now is trying to figure out where the memory is going, and ho= w=20 to prevent it. :) Can anyone help me diagnose this? =2D --=20 Jonathan Fosburgh AIX and Storage Administrator UT MD Anderson Cancer Center Houston, TX =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAB/MjqUvQmqp7omYRApjEAJ9OV528bLfHPMHuEQ8HxdNzWZ08fACgviCM fqx0/5bPTnuNHiXy1rC6+uE=3D =3DMZoB =2D----END PGP SIGNATURE----- From owner-freebsd-x11@FreeBSD.ORG Fri Jan 16 06:47:06 2004 Return-Path: Delivered-To: freebsd-x11@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2ADC716A4CE; Fri, 16 Jan 2004 06:47:06 -0800 (PST) Received: from theinternet.com.au (c211-30-103-113.carlnfd1.nsw.optusnet.com.au [211.30.103.113]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8C75243D5F; Fri, 16 Jan 2004 06:46:48 -0800 (PST) (envelope-from akm@theinternet.com.au) Received: from theinternet.com.au (akm@localhost [127.0.0.1]) by theinternet.com.au (8.12.9/8.12.9) with ESMTP id i0GEkitN073922; Sat, 17 Jan 2004 01:46:44 +1100 (EST) (envelope-from akm@theinternet.com.au) Received: (from akm@localhost) by theinternet.com.au (8.12.9/8.12.9/Submit) id i0GEkhjL073921; Sat, 17 Jan 2004 01:46:43 +1100 (EST) Date: Sat, 17 Jan 2004 01:46:43 +1100 From: Andrew Kenneth Milton To: Jonathan Fosburgh Message-ID: <20040116144643.GF57209@zeus.theinternet.com.au> References: <200401160820.19794.jonathan@fosburgh.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200401160820.19794.jonathan@fosburgh.org> User-Agent: Mutt/1.4.1i cc: freebsd-x11@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: Possible memory leak in XFree86 X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Jan 2004 14:47:06 -0000 +-------[ Jonathan Fosburgh ]---------------------- | -----BEGIN PGP SIGNED MESSAGE----- | Hash: SHA1 | | I am cross-posting this to -current, since the problem is occuring in that | environment. [snip] | What is happening is that the X server slowly allocates more memory until all | physical RAM and page space are allocated, and the pager starts killing off | processes, eventually killing the X server. [snip] My X 4.3.0 Server under -current doesn't really go above 150M, I've got a radeon, DRI enabled. I also run xscreesaver and DPMS. I've never had it go bananas like you're describing. I also run at a fairly high res (1920 x 1440). drm0: port 0xd800-0xd8ff mem 0xe7000000-0xe700ffff,0xe8000000-0xefffffff irq 11 at device 0.0 on pci1 I'm using Windowmaker and wdm, a combination of Mozilla and Opera for browsing, both of which are resource hungry and buggy. -- Totally Holistic Enterprises Internet| | Andrew Milton The Internet (Aust) Pty Ltd | M:+61 416 022 411 | ACN: 082 081 472 ABN: 83 082 081 472 |akm@theinternet.com.au| Carpe Daemon From owner-freebsd-x11@FreeBSD.ORG Fri Jan 16 10:15:34 2004 Return-Path: Delivered-To: freebsd-x11@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 53F7A16A4CE; Fri, 16 Jan 2004 10:15:34 -0800 (PST) Received: from rwcrmhc11.comcast.net (rwcrmhc11.comcast.net [204.127.198.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id A938143D2F; Fri, 16 Jan 2004 10:15:32 -0800 (PST) (envelope-from eta@lclark.edu) Received: from [192.168.0.103] (c-24-21-18-195.client.comcast.net[24.21.18.195]) by comcast.net (rwcrmhc11) with SMTP id <2004011618153201300aah6ie>; Fri, 16 Jan 2004 18:15:32 +0000 From: Eric Anholt To: Jonathan Fosburgh In-Reply-To: <200401160820.19794.jonathan@fosburgh.org> References: <200401160820.19794.jonathan@fosburgh.org> Content-Type: text/plain Message-Id: <1074277065.725.4.camel@leguin> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Fri, 16 Jan 2004 10:17:45 -0800 Content-Transfer-Encoding: 7bit cc: freebsd-x11@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: Possible memory leak in XFree86 X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Jan 2004 18:15:34 -0000 On Fri, 2004-01-16 at 06:20, Jonathan Fosburgh wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > I am cross-posting this to -current, since the problem is occuring in that > environment. > > I first noticed this as far back as 5.0-RELEASE, but I had chalked it up to > being hardware-related, for reasons I shall get into shortly. The problem > has persisted throught XFree86 4.3.x (and through the most current snapshot > available in the ports). I am also running KDE 3.x (3.1.x and now 3.2 > BETA2). I am running -CURRENT (updated within the past couple of weeks) on a > Pentium III-600mHz with 383MB (from dmesg) RAM. Originally, I had an nvidia > Riva TNT2 video card. For a brief time I used the nvidia drivers, but those > were so unstable I never found out if this particular problem was > reproduceable with them. I now have an ATI Radeon 9200 and I see the same > things. > > What is happening is that the X server slowly allocates more memory until all > physical RAM and page space are allocated, and the pager starts killing off > processes, eventually killing the X server. This seems to screw up syscons > as well, and I wind up having to reboot to get my text consoles back. > Things have gotten slightly better of late, sometimes the memory is freed and > the XFree86 process might go from say 400+MB (according to top) down to a > little less then 200MB, which appears to be normal for the Radeon using DRI. > But this is not always the case. When I come in in the mornings I either > find my system very low on page space, or if I am gone for a couple of days I > will generally find that X has been killed. I run screensavers and have DPMS > set up to send the monitor to power-save mode. I have reduced my screensaver > to just blanking the screen, but still to no avail. This morning, I came in > (after having been out yesterday) to find that X had been killed after > running out of page space. > > Now, here is why I initially thought it was hardware related (that is, in the > nvidia driver for XFree86): at home I have a Pentium III-600 with about the > same amount of memory, running XFree86 4.3.x, KDE 3.1.x, screensavers, DPMS, > etc. The differences are that at home I have an SiS ViRGE video card > (incidentally, PCI versus AGP for work), and I am tracking -STABLE there. > Only every once in awhile do I run out of page space at home, but my paging > space is undersized there, whereas at work it is set to the recommended size > from when I did the install, 753MB. > > Where I am at now is trying to figure out where the memory is going, and how > to prevent it. :) Can anyone help me diagnose this? Every month or so I see someone saying they think XFree86 is leaking memory. Of course, with this release of XFree86 having been out for about a year now, there are probably no major memory leaks, especially with such a commonly used driver like ATI. The X Server allocates memory on behalf of clients. What you are seeing, I'm willing to bet, is some application you run is leaking pixmaps, so the X Server continues allocating memory for it until OOM killer starts killing things off. You could try, when the memory usage is very large, killing your apps off one by one and seeing when the memory usage in the server goes back down. -- Eric Anholt eta@lclark.edu http://people.freebsd.org/~anholt/ anholt@FreeBSD.org From owner-freebsd-x11@FreeBSD.ORG Fri Jan 16 11:19:15 2004 Return-Path: Delivered-To: freebsd-x11@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 007AB16A4CE; Fri, 16 Jan 2004 11:19:15 -0800 (PST) Received: from mail.mdacc.tmc.edu (mail.mdanderson.org [143.111.251.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id 978EA43D45; Fri, 16 Jan 2004 11:19:13 -0800 (PST) (envelope-from jonathan@fosburgh.org) Received: from ([143.111.64.231]) by mail.mdacc.tmc.edu (InterScan E-Mail VirusWall Unix); Fri, 16 Jan 2004 13:18:35 -0600 (CST) From: Jonathan Fosburgh To: Eric Anholt Date: Fri, 16 Jan 2004 13:11:33 -0600 User-Agent: KMail/1.5.94 References: <200401160820.19794.jonathan@fosburgh.org> <1074277065.725.4.camel@leguin> In-Reply-To: <1074277065.725.4.camel@leguin> MIME-Version: 1.0 Content-Disposition: inline Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message-Id: <200401161311.37284.jonathan@fosburgh.org> cc: freebsd-x11@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: Possible memory leak in XFree86 X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Jan 2004 19:19:15 -0000 =2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Friday 16 January 2004 12:17 pm, Eric Anholt wrote: > > Every month or so I see someone saying they think XFree86 is leaking > memory. Of course, with this release of XFree86 having been out for > about a year now, there are probably no major memory leaks, especially > with such a commonly used driver like ATI. > > The X Server allocates memory on behalf of clients. What you are > seeing, I'm willing to bet, is some application you run is leaking > pixmaps, so the X Server continues allocating memory for it until OOM > killer starts killing things off. You could try, when the memory usage > is very large, killing your apps off one by one and seeing when the > memory usage in the server goes back down. I will admit that part of why I hadn't previously reported it (in addition = to=20 thinking that my prior hardware had something to do with it) was that I wou= ld=20 have expected seeing people screaming about this if it really was a problem= =20 in X itself (or at least running on FBSD(-CURRENT). Weighing against that,= =20 however, is the fact that I do not see this at home running the same=20 software, the same configuration (I configure KDE the same way, etc) and=20 basically the same apps. However, I will see if I can start with disabling= =20 kscreensaver entirely (that may or may not work for me, since I think the=20 screensaver has to be active to lock the display) and see if that helps ove= r=20 the long weekend. =2D --=20 Jonathan Fosburgh AIX and Storage Administrator UT MD Anderson Cancer Center Houston, TX =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFACDdoqUvQmqp7omYRAqgkAJ9Ow8JVHAqI/hLKFssp/Gl9U8agfACfYKm0 Eg5NuLkIPp3HF4cEI0RKosU=3D =3DGyb+ =2D----END PGP SIGNATURE----- From owner-freebsd-x11@FreeBSD.ORG Fri Jan 16 12:02:06 2004 Return-Path: Delivered-To: freebsd-x11@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E507A16A4CE for ; Fri, 16 Jan 2004 12:02:06 -0800 (PST) Received: from almso1.proxy.att.com (almso1.att.com [192.128.167.69]) by mx1.FreeBSD.org (Postfix) with ESMTP id 48E5C43D1D for ; Fri, 16 Jan 2004 12:02:04 -0800 (PST) (envelope-from jwb@homer.att.com) Received: from ulysses.homer.att.com ([135.205.193.8])i0GK23Tq014279 for ; Fri, 16 Jan 2004 15:02:03 -0500 Received: from akiva.homer.att.com (akiva.homer.att.com [135.205.212.39]) by ulysses.homer.att.com (8.9.3/8.9.3) with ESMTP id PAA25230 for ; Fri, 16 Jan 2004 15:01:16 -0500 (EST) Received: from akiva.homer.att.com (localhost [127.0.0.1]) by akiva.homer.att.com (8.11.7+Sun/8.9.3) with ESMTP id i0GK1Go10545 for ; Fri, 16 Jan 2004 15:01:16 -0500 (EST) Message-Id: <200401162001.i0GK1Go10545@akiva.homer.att.com> To: x11@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <10542.1074283275.1@akiva.homer.att.com> Date: Fri, 16 Jan 2004 15:01:16 -0500 From: "J. W. Ballantine" Subject: FreeBSD Port: XFree86-4-4.3.0 Build Failure X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Jan 2004 20:02:07 -0000 This is a resend of a large prior send, without the build script. I'm trying to build the XFree86-4 meta-port and it fails with GccWarningOptions: No such file or directory. Also there is no /etc/make.conf. This is on a 4.9-stable system with the ports ctm to current this morning. I cd to the ports dir, and then did make clean ; make deinstall ; make install clean. ( I've attached the build script. ) Any pointers as to what the problem is?? Thanks Jim From owner-freebsd-x11@FreeBSD.ORG Sat Jan 17 07:53:57 2004 Return-Path: Delivered-To: freebsd-x11@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 285C016A4CE; Sat, 17 Jan 2004 07:53:57 -0800 (PST) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 758E443D55; Sat, 17 Jan 2004 07:53:56 -0800 (PST) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) i0HFruFR088185; Sat, 17 Jan 2004 07:53:56 -0800 (PST) (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.12.10/8.12.10/Submit) id i0HFru60088181; Sat, 17 Jan 2004 07:53:56 -0800 (PST) (envelope-from linimon) Date: Sat, 17 Jan 2004 07:53:56 -0800 (PST) From: Mark Linimon Message-Id: <200401171553.i0HFru60088181@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-ports-bugs@FreeBSD.org, x11@FreeBSD.org Subject: Re: ports/61470: [patch] fix build of x1-toolkits/xrender X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Jan 2004 15:53:57 -0000 Synopsis: [patch] fix build of x1-toolkits/xrender Responsible-Changed-From-To: freebsd-ports-bugs->x11 Responsible-Changed-By: linimon Responsible-Changed-When: Sat Jan 17 07:53:45 PST 2004 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=61470