Date: Wed, 7 Aug 2002 17:25:04 -0500 From: Christopher Farley <chris@northernbrewer.com> To: Edwin Groothuis <edwin@mavetju.org> Cc: Philip Hallstrom <philip@adhesivemedia.com>, Stacey Roberts <sroberts@dsl.pipex.com>, FreeBSD-Gnome <freebsd-gnome@FreeBSD.ORG>, FreeBSD-Questions <freebsd-questions@FreeBSD.ORG> Subject: Re: Mozilla's so slow! Message-ID: <20020807222500.GA17759@northernbrewer.com> In-Reply-To: <20020708231515.GB577@k7.mavetju> References: <20020707013753.GA577@k7.mavetju> <20020708100812.E1306-100000@cypress.adhesivemedia.com> <20020708231515.GB577@k7.mavetju>
next in thread | previous in thread | raw e-mail | index | archive | help
Edwin Groothuis (edwin@mavetju.org) wrote: > > I have a similar problem... not as bad as this other fellows, but still > > quite noticable. And it's not a DNS thing... I can type in a url, click > > go, watch it while it "resolves..." and in the meantime open up an xterm > > and ping that server, nslookup it, telnet to it, etc... instantly... and > > even then mozilla still waits and waits and waits... > > I wouldn't mind seeing some URLs on which you have this behaviour. Sorry to chime in so late, but try any site at vanguard.com (www.vanguard.com), or any site that does advertising with doubleclick.net, such as the www.washingtonpost.com. Watch the status bar as it attempts to resolve ad.doubleclick.net; it takes at least 40 seconds, and during that time, all other mozilla windows are blocked. (That is the worst thing!) I think the problem is that these sites use a DNS with a broken IPv6 implementation that wreaks havoc with mozilla. A workaround is to compile a kernel with IPv6 disabled. Mozilla works fine, then. -- Christopher Farley www.northernbrewer.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020807222500.GA17759>