Closed Bug 596961 Opened 15 years ago Closed 14 years ago

Connecting through IPv6 hangs Firefox

Categories

(Core :: Networking, defect)

Product:
Core
Component:
Networking
Platform:
x86
Windows XP
Type:
defect
Priority:
Not set
Severity:
major

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: timofei.shatrov, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:2.0b6) Gecko/20100101 Firefox/4.0b6 Build Identifier: Mozilla/5.0 (Windows NT 5.1; rv:2.0b6) Gecko/20100101 Firefox/4.0b6 OK, this one has been bothering me for a while, might as well file a bug. There is IPv6 access in our dormitory network, and unlike IPv4 access it's not metered. Every single application that supports IPv6 (Google Chrome, uTorrent, sabnzbd) works on my computer with default settings. Unfortunately, Firefox does not. Every single version from at least Firefox 3.5 to the latest Firefox nightlies contains this bug. I tested this on my desktop and my netbook, with or without empty profile. Here's what happens: I type a URL of an IPv6 enabled website in the address bar (i.e. "http://www.youtube.com") The status bar says "Connecting to www.youtube.com", but the page stays blank. Meanwhile CPU usage goes to the max, and Firefox becomes unable to connect to any other site (even IPv4 ones). The only solution is to close Firefox. I don't have an access to another IPv6-enabled network, so I can't test if there is something wrong with how our campus network is configured or something else. I also am not aware of any other people having this issue. Reproducible: Always Steps to Reproduce: 1. Make sure network.dns.disableIPv6 is "false". 2. Go to www.youtube.com Actual Results: Firefox never connects to the site. No errors are displayed. Status bar says "Connecting to www.youtube.com". CPU usage takes over a single core. Firefox UI remains responsive, but it's not possible to connect to anything again. Expected Results: Firefox connects to www.youtube.com and displays the website's content (just as Google Chrome does on my computer). I will provide any kind of debug information that might help.
See Bug 136898 - does one of those dependent bugs cover your issue?
Version: unspecified → Trunk
None of these look like the bug I had. Since I filed that bug, I have actually successfully used Firefox 4 with IPv6, so whatever was causing it is no longer around. I don't have IPv6 connectivity at all right now, so I cannot test it *shrugs*.
Component: General → Networking
Product: Firefox → Core
QA Contact: general → networking
WFM per reporter comment 2
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.