From owner-freebsd-current  Fri Mar 15 22:15:48 2002
Delivered-To: freebsd-current@freebsd.org
Received: from avocet.prod.itd.earthlink.net (avocet.mail.pas.earthlink.net [207.217.120.50])
	by hub.freebsd.org (Postfix) with ESMTP id 0A2C537B405
	for <current@freebsd.org>; Fri, 15 Mar 2002 22:15:44 -0800 (PST)
Received: from pool0129.cvx22-bradley.dialup.earthlink.net ([209.179.198.129] helo=mindspring.com)
	by avocet.prod.itd.earthlink.net with esmtp (Exim 3.33 #1)
	id 16m7Tc-0007dk-00; Fri, 15 Mar 2002 22:15:36 -0800
Message-ID: <3C92E2DD.4A957A4A@mindspring.com>
Date: Fri, 15 Mar 2002 22:14:53 -0800
From: Terry Lambert <tlambert2@mindspring.com>
X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony}  (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Dag-Erling Smorgrav <des@ofug.org>
Cc: Garrett Wollman <wollman@lcs.mit.edu>,
	"Brian T.Schellenberger" <bts@babbleon.org>, current@FreeBSD.ORG
Subject: Re: gcc -O broken in CURRENT
References: <20020315205228.V32037-100000@alpha.yumyumyum.org>
		<20020316034126.2DA6CBA05@i8k.babbleon.org>
		<200203160426.g2G4QKH02078@khavrinen.lcs.mit.edu> <xzpwuwdw19y.fsf@flood.ping.uio.no>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-current.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-current>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-current>
X-Loop: FreeBSD.ORG

Dag-Erling Smorgrav wrote:
> Garrett Wollman <wollman@lcs.mit.edu> writes:
> > What problems do you have with it?
> 
> Slow.  Eats memory.  Crashes all the time.  Does not save state
> between sessions.  Does not render HTML 4 properly.  Does not support
> CSS properly.  Does not zoom.  Does not display PNG properly.
> Incorrectly ignores cache-control headers on images.  The list goes
> on...

If you use a real network socket instead of the shared memory
extension, it won't eat memory.  THis lost memory due to it
instancing regions for which it loses the reference counts;
it's arguably a resource tracking bug in the X server, actually,
since they are associated with windows that go away.

I admit, this is an annoying one...

-- Terry

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message