1112365 - Page/Requests fail to load under IPv6 (dualstack)

Status: RESOLVED DUPLICATE of bug 1123324

(Core :: Networking: DNS, defect)

Description

[Valentin Gosu [:valentin] (he/him)]

The issue reproduces in several ways. Sometimes the page doesn't load, sometimes only the comments, and sometimes times it's other elements (it can be seen under devtools that they don't load)

How to reproduce:
Open dev-tools, network tab
Load https://www.facebook.com/thedoghousediaries
If page loads, click the "Load X more comments' button on one of the posts.
2 out of 3 times this times out for me.

Will attach logs immediately.

Comment 1

[Valentin Gosu [:valentin] (he/him)]

Attachment: comments_timeout_ipv6.txt

The DNS table from about:networking is pasted in the file.

Comment 2

[Valentin Gosu [:valentin] (he/him)]

Some of the logs are quite large. Uploaded them here https://drive.google.com/folderview?id=0BwxJSOG4k8xDVHNzRTF5Z2ZlZ0k&usp=sharing (log_ipv4.txt is just for reference, it works when the disableIPv6 pref is set)

Comment 3

[Alexander Ploner]

I have the same issue with Firefox on my MacBook Pro and domains that are hosted by Google (e.g. apis.google.com, www.google.de, drive.google.com, fonts.google.com ...). This is really annoying because Google scripts are embedded into many many websites.

I tested the behavior in Firefox Release 35, Beta 36 and Nightly 38 - the problem is always the same.
Setting the value of network.dns.disableIPv6 to true solved the issue for me also. Firefox for Android works without any problems in the same WiFi. Other browsers like Opera, Safari and Chrome do not have that problem on the same MacBook.

@Valentin, which operating system did you use when this problem occurred? Was it OS X also? I'm currently using OS X Yosemite 10.10.1.

Comment 4

[Valentin Gosu [:valentin] (he/him)]

The logs are on Linux, but I've also encountered the problem on OS X.

Comment 5

[Alexander Ploner]

I've updated OS X from 10.10.1 to 10.10.2 on the 30th of January and read the following two points within the update description [1]:
- Resolves an issue that might cause Wi-Fi to disconnect
- Resolves an issue that might cause web pages to load slowly

While the first thing is something they write in about every update the second sounded interesting. I've set network.dns.disableIPv6 back to false immediately after installing the update and had no more problems since then. The problem seems to be fixed for me now - but it's still a strange thing anyway because it happened only in Firefox and only with websites hosted by Google.

Maybe this information helps to figure out the problem (maybe also on Linux).

[1] http://support.apple.com/en-us/HT204210

Comment 6

[Dragana Damjanovic [:dragana]]

Looking at log attached here this is the same issue as bug 1123324.
But looking at log from comment 2 "log_ipv6.txt" I do not see any dns error. Can it be that this is also a log with ipv6 disabled?

Comment 7

[Valentin Gosu [:valentin] (he/him)]

I'm fairly sure ipv6 isn't disabled as there are IPv6 addresses in the log (search for ::1).
However, the logs in log_startup_cant_load_domain.txt might be closely related to bug 1123324

Comment 8

[Dragana Damjanovic [:dragana]]

log_ipv6_e10s.txt has error that confirms that is the same issue as 1123324. log_startup_cant_load_domain.txt touches the error-prone part of the code as well.

so marking it as duplicate.

Comment 10

[Alexander Ploner]

(In reply to Dragana Damjanovic [:dragana] from comment #9)
> *** This bug has been marked as a duplicate of bug 123324 ***

You made a small typo its bug 1123324 not bug 123324.
(I can't fix this with my account :(.)

Comment 11

[Alexander Ploner]

(In reply to Alexander Ploner from comment #5)

Additional note:
The described problem is now occurring again, which means that it has not been fixed with the OS X update. This time it's in Firefox DeveloperEdition/Aurora (I'm using Nightly and Aurora at the same time) but again with Google sites.

Comment 13

[Dragana Damjanovic [:dragana]]

Thanks for noticing typo.

The fix is still only in Nightly. I will ask for a uplift next week. It should run for some days on Nighty to be sure it is not breaking anything. And I need to make an additional fix for some corner cases that I have missed.