Closed
Bug 164988
Opened 22 years ago
Closed 22 years ago
DNS: Interrupted page loads can cause blocks
Categories
(Core :: Networking, defect)
Core
Networking
Tracking
()
VERIFIED
DUPLICATE
of bug 164593
People
(Reporter: sharding, Assigned: gordon)
Details
(Keywords: helpwanted)
(From my comment in Bug 146769): There seems to be a small window of time (in all likelihood, during the DNS resolution) in which hitting "stop" for a page load will make all Mozilla DNS lookups block for some time. For example, I just had the following happen: 1. Type http://www.cnn.com/ in the location bar and hit enter 2. Almost immediately hit "stop" (I suspect, but have not confirmed, that this must happen before the DNS lookup has completed) 3. All subsequent attempted page loads which required new (non-cached) DNS information hung for a couple of minutes. Then everything went back to normal. Additional page loads from sites I'd already been at (thus, DNS info was probably cached) worked fine. nslookup on the hostnames for the blocked load attempts also worked fine. I see this a couple of times a week on average. Currently I'm using build 2002082608 on FreeBSD, but I've seen this (or similar) problems on builds for a long time and also on MacOS X.
I've seen this for a while on all platforms.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: helpwanted
OS: Linux → All
Hardware: PC → All
Summary: Interrupted page loads can cause DNS blocks → DNS: Interrupted page loads can cause blocks
Comment 2•22 years ago
|
||
I wonder if this the same as what I saw in bug 153589.
I have something much worse, and similar to this. Interner Explorer doesn't have any of the problems when I check it at the same time with mozilla. I am working inside a company firewall. This is not the firewall since IE works fine. When I try to access company sites(intranet) there is no problem. When I try to access all outside sites(internet) mozilla gives a status-bar message of the type "Resolving host HOSTNAME..." but doesn't resolve any site. The following actions didn't help: clearing history, clearing disk and memory cache, restarting mozilla, and reinstalling a newer version!!! I have the problem for several days(everything worked fine before) I am using build 2002092308 Are there any workaround steps that someboy can suggest (apart from what I tried)?
*** This bug has been marked as a duplicate of 164593 ***
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•