User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1b1) Gecko/20081007 Firefox/3.1b1 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1b1) Gecko/20081007 Firefox/3.1b1 Firefox (3.0.1-4 and 3.1b1-4) all freeze on websites which have their DNS servers incorrectly setup which going through a proxy server. Facebook does not have its DNS records correctly set for AAAA and therefore returns SERVFAIL but not instantly, but after 4-5 seconds. Firefox is trying to look up the domain's IPv6 address and hangs while it is waiting. The bug is two-fold: 1) The JavaScript engine should not be looking up the domain in the first place since it is using a proxy and therefore that will look it up itself. 2) Firefox should not hang while doing DNS queries such that none of the other tabs are available and the window cannot be rendered. This does not occur on the same network and version on Windows. Utilising gdb I have found the issue seems to be in the library libxul when it calls pthread_wait_cond. But strace showed the lagging to occur during a DNS query. We have managed to stop the browser freezing by disabling IPv6 lookups, but it should not be looking the IP up anyway. Reproducible: Always Steps to Reproduce: 1. Have IPv6 lookups turned on (network.dns.disableIPv6 = false) 2. Use a proxy server (preferably squid-based to resemble conditions) 3. Navigate to www.facebook.com (from uk) 4. Watch Firefox (3.0.1-3.0.4 and 3.1b1-4) freeze while it tries to get the non-existent AAAA records. Actual Results: The browser freezes and the window does not render. It also utilises 100% CPU. Expected Results: The browser should remain operable while the DNS query is executing.

The DNS part of the bug is related to 390304 I believe. Although, it still should not lock up the system when doing DNS queries in the JavaScript engine.

The lock up is bug 235853, almost certainly.

This is a mass search for Firefox General bugs filed against version 3.0 that are UNCO and have not been changed for 200 days. Reporter, please update to Firefox 3.6.10 or alter. Firefox 3.0 is no longer supported and is no longer receiving updates. After you update, please create a fresh profile, http://support.mozilla.com/kb/managing+profiles, and test to see if your bug still exists. If you still the bug, then please post a comment with the version you tested against, and the problem. If the issue is no longer there, please set the RESOLUTION to RESOLVED, WORKSFORME.

No reply from reporter, INCOMPLETE. Please retest with Firefox 3.6.12 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.