Bug#489944: iceweasel: application/window freezes if DNS does not respond

[Mike Hommey]

Hi,

Sorry for the delayed answer.

On Tue, Jul 08, 2008 at 10:44:13PM +0200, Paolo wrote:
> Package: iceweasel
> Version: 2.0.0.14-0etch1
> Severity: important
> 
> Hi,
> 
> I think .14 is severely broken, iirc .13 wasn't that much bad - either the
> whole 'net (or the DNS at least) has  slowed down by an order of magnitude,
> or Firefox got a bad commit lastly.
> 
> Fact is, that I'm killing FF/IW the hard way quite often, it simply freezes
> whenever it doesn't get an answer from DNS (or the site); if DNS (or the 
> site) never answers, it hangs forever, but in any case till DNS answers 
> it's completely out of reach, no way to stop it but via a solid SIGKILL.
> 
> That's what I observed, that is; but it might be that it gets confused/fooled
> by (proxy)filtered content, eg waiting for content definitely cut off by
> privoxy(1). Other browsers work, though. And, as said, iirc .13 wasn't 
> _that_ bad, at least not to the point to force me to switch browser.
> 
> Dillo(1) along the same net-path (ie same pc, local proxy (privoxy)) works
> quite fine - ie laods reachable URLs, waits/timesout on those that don't 
> respond (either the URL itself or the DNS for such) but it stay responsive 
> to user control.
> 
> Of course, Dillo can't cope with most bloa^H^H^H^Hfeatures-rich sites, so
> I had to switch to Opera, at least temporarily.

Can you still reproduce these issues with a newer version of iceweasel,
from either lenny or squeeze ?

Cheers,

Mike