1347054 - Pages are not loading when using WiFi (possible interaction with Chromecast/similar devices in same network)

Status: RESOLVED DUPLICATE of bug 1347755

(Firefox for Android Graveyard :: General, defect)

Description

[becker.nick.a]

Attachment: screenshot01.png

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Firefox/52.0
Build ID: 20170302120751

Steps to reproduce:

Connected to my home WiFi network. Opened up Firefox app. Entered google.com in address bar.

No add-ons installed. Running fresh install of Firefox 52.0 on Android 6.0.1.


Actual results:

Page does not load. Orange progress bar advances about 20%.

Many users are experiencing this problem: https://support.mozilla.org/t5/Firefox-for-Android/Firefox-for-Android-not-working-when-WiFi-is-on-but-works-when/td-p/1373086/page/2


Expected results:

Page should have loaded. After switching to mobile data, pages load just fine.

Comment 2

[Jan Henning [:JanH]]

Also interesting comment from the support forum:
> I just found out that in my case it's not a problem if the devices are connected via WiFi (with mobile data they are always fine), but if my Smart TV is turned on. Yes, you read correctly. A Smart TV running Android TV.
> As soon as the TV is turned on, Firefox becomes unusable on my devices, even though both were working properly up until the TV was enabled. As soon as the TV is turned off, Firefox force closed and restarted, everything is back to normal and I can surf the web.

Comment 3

[Bret Mogilefsky]

I have this problem as well, running Firefox 52.0 on Android 6.0.1 on a Nexus 7 device (meaning it has WiFi, but no mobile data). 


I've uninstalled Firefox and reinstalled it clean, and this did not resolve the problem. There is no system-wide proxy set. The problem appears over both 5GHz and normal WiFi networks. 

In case it's relevant (per the thread referenced above): I do have two Chromecasts in my home network. The problem appears whether about:config has browser.casting.enabled set to true or false.

Chrome and all other apps appear to be working fine under the same conditions.

Comment 4

[Bret Mogilefsky]

UPDATE: 
* I unplugged both Chromecast devices. Suddenly Firefox was zippy, with no problems loading anything. 
* I plugged both Chromecast devices back in and without restarting, Firefox was suddenly quite slow... Sites were loading, but only after 20-30 seconds.
* I restarted Firefox. Back to orange loading bar at 20% for about 30 seconds, then a blank tab, on any URL.

There's some kind of interaction with Chromecast devices causing this, even when browser.casting.enabled is false.

Comment 5

[Nevin Chen(Not active on Bugzilla)]

May I know what page were you looking at? Thank you!

Comment 6

[Paul M]

I too have this new Firefox 52.0 problem (taking minutes to load any page, if ever) on both my Tesco HUDL 2 tablet (Android 5.1) and my Samsung Galaxy S5 Mini (Android 6.01). They fail when connected to both my main AP (a BT Home Hub 3 provided by my ISP, British Telecom) and my repeater AP (TP-LINK CPE210). Both are secure connections using 2.4GHz WPA/WPA2 (default settings).

On my WiFi-only tablet, I also get a blank screen when I try to display 'about:firefox'; it is then OK when I turn WiFi off (phone not tried).

Curiously Firefox works on both devices correctly when I connect via a second OPEN SSID on the Home Hub 3. This SSID has a landing page requiring credentials and is a standard feature of the AP provided by my ISP for community use. My successful connection used an app 'BTWiFi' that automatically connects using my already-configured credentials.

Firefox works correctly on my phone when using mobile data.

Comment 7

[Richard Newman [:rnewman]]

Who still remembers how our SSDP implementation works?

That sounds like the culprit…

Comment 8

[Bret Mogilefsky]

(In reply to Nevin Chen [:nechen] from comment #5)
> May I know what page were you looking at? Thank you!

All URLs were affected. I was using https://google.com and https://cnn.com as my test pages while unplugging and replugging Chromecast devices, though.

Comment 10

[Paul M]

Update to Comment #6:

Further testing has shown that, if power is removed from the Chromecast device that I have on my network, the bug clears. Unlike others, I do not need to actally cast to see the bug, just have the chromecast device on the network.

This explains the different behaviour I saw across different WiFi APs.

Comment 11

[Bret Mogilefsky]

Is anyone looking at this bug? Firefox is basically unusable under these conditions. It's bad enough that I've switched back to using Chrome daily now.