Closed Bug 15762 Opened 25 years ago Closed 25 years ago

Loading first page on isolated lan take about 4 1/2 minutes

Categories

(Core :: Networking, defect, P3)

Product:
Core
Component:
Networking
Platform:
x86
Windows 95
Type:
defect

Tracking

()

Status:
VERIFIED DUPLICATE of bug 10731

People

(Reporter: pawyskoczka, Assigned: jud)

References

Details

As far as the isolated lan problems goes, this is what happens now .  The first time you load a page ( http://
208.12.38.99/aol )  the page is displayed in about 4 1/2 minutes.  All subsequent page loads are normal, 3 or 4 secs.  Not sure what
is going on here.  Jud, I opened this bug as it effects our performance testing.  I know you will be here next week and then maybe you
can look at it as the lab is close by.
QA Contact: tever → paw
changed qa contact to paw@netscape.com since it is more likely that I will verify the fix.
Target Milestone: M11
Putting on M11.  Blocking QA...taking too long to run a small set of tests.
More info.  Mac work fine, no delay.  However, both Windows and Linux have a delay on loading the first page.  Generally, Windows 95
take twice as long to load as Linux.  Windows take between 2 - 4 minutes and linux take 1-2 minutes to load the AOL site locally.
Blocks: 11349
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
This is a result of synchronous dns requests blocking everything until they fail
via the timeout. Once we have async dns, this goes away.


Note: that the current workaround employed in the lab is working.

*** This bug has been marked as a duplicate of 10731 ***
Status: RESOLVED → VERIFIED
Bulk move of all Necko (to be deleted component) bugs to new Networking

component.
You need to log in before you can comment on or make changes to this bug.