Date: Fri, 15 Mar 2002 22:14:53 -0800 From: Terry Lambert <tlambert2@mindspring.com> 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 Message-ID: <3C92E2DD.4A957A4A@mindspring.com> References: <20020315205228.V32037-100000@alpha.yumyumyum.org> <20020316034126.2DA6CBA05@i8k.babbleon.org> <200203160426.g2G4QKH02078@khavrinen.lcs.mit.edu> <xzpwuwdw19y.fsf@flood.ping.uio.no>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3C92E2DD.4A957A4A>