Closed Bug 391682 Opened 18 years ago Closed 18 years ago

Firefox uses synchronious blocking DNS requests that stall whole application for tens of seconds when roken DNS names do not resolve due to timeout

Categories

(Firefox :: General, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 235853

People

(Reporter: don_oles, Unassigned)

References

()

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.6) Gecko/20070725 Firefox/2.0.0.6 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.6) Gecko/20070725 Firefox/2.0.0.6 At least when using proxy auto configuration, browsing a page that references some URL's that do not resolve in DNS and DNS server does not respond immediately, makes the whole firefox application hang for a while, causing a Windows OS tell that 'application does not respond', inability to do anything with any open page or tab, possibly time-out other downloads in manager. The only thing a user can do is 1) relax and wait a minute and close that page and never return there 2) close firefox and reopen, so the session resumes without the last tab open, the one with broken page. I do not know what exact part of application/OS causes this behavior, but it has to be mended. If it is OS problem, there has to be a workaround. The same problem our world experienced long ago with Internet Explorer family browsers, I had a hope that in 21-th century programmers that build the new-generation browser are smart enough not to repeat this awful errors, but hope turned out to be vain. Reproducible: Always Steps to Reproduce: Go to example page. Expected Results: At least allow a user to close bad page, or not to display element that can not be loaded, but not stop the whole world cause some DNS server went down to black hole.
I concur.
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.