1619061 - I cannot open webpage, no error, blank page, inactive refresh button

Status: UNCONFIRMED

(Core :: Networking, defect, P2)

Description

[gwarser]

Attachment: log.txt-main.7825.moz_log.gz

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:75.0) Gecko/20100101 Firefox/75.0

Steps to reproduce:

Open https://electrek.co/2020/02/26/tesla-secret-roadrunner-project-battery-production-massive-scale/ (Paste & Go).

Actual results:

After a while loading stops, page is blank, refresh button is inactive, I see only URL in address bar.

Expected results:

Page should open or at least error should be shown.

This issue is present on 75.0a1 20200228161940, 74.0b6 and 73.0.1

but not on 68.4.2esr where page loads fine.

Chrome shows error page with ERR_CONNECTION_CLOSED message and retries connecting after a while and succeeds.

Attached log from about:networking

Comment 1

[gwarser]

Attachment: retry attempts.png

Comment 2

[gwarser]

Attachment: Chrome error, autotrying to reconnect.png

Comment 3

[gwarser]

After update to latest ESR I'm now seeing it here too. And seems to be worse, because URL sometimes resets to about:blank.

Comment 4

[Raluca Popovici, Desktop QA]

I was unable to reproduce the issue you've reported in any of the latest Firefox versions on Win 10 or Ubuntu 18.04.

Please test if the issue occurs in safe mode. Here is a link that can help you do that:
https://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode

If the issue still persists, please test it using a new profile, you can find the steps to do that below:
https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles?redirectlocale=en-US&redirectslug=Managing-profiles#w_starting-the-profile-manager

Comment 5

[gwarser]

(In reply to Raluca from comment #4)

I was unable to reproduce the issue you've reported in any of the latest Firefox versions on Win 10 or Ubuntu 18.04.

This happened with very bad network conditions - limited 3g connection and system update downloading in background. If you can try limiting you connections to something like EDGE speeds (up to 30kB/s) and delays/pings measured in seconds?

Please test if the issue occurs in safe mode. Here is a link that can help you do that:

This was tested in completely new profiles.

---

My point was: Chrome can recover even in very bad network conditions, where Firefox fails considerably - does not show any error page, does not retry automatically, interface is not working properly (reload is inactive) and does not allow to easily retry manually (reload inactive, no "Go" button, in worst case URL is lost to about:blank)

Comment 6

[gwarser]

In case you missed - network log is attached in description. It was simply: start logging, try navigating to URL, load fails, stop logging.

Comment 7

[gwarser]

Attachment: log.txt-main.13285.moz_log.gz

Another log (I recorded two then).

Comment 8

[gwarser]

Version 79.0a1
Build ID 20200606094603
User Agent Mozilla/5.0 (X11; Linux x86_64; rv:79.0) Gecko/20100101 Firefox/79.0
OS Linux 5.4.43-1-MANJARO #1 SMP PREEMPT Wed May 27 20:25:12 UTC 2020

I happened again just now. I cannot open https://forum.manjaro.org/t/stable-update-2020-06-06-linux-5-7-0-firefox-77-and-78-arc-themes-software-center-haskell-python/146837

I works fine in new private window, but does not work in new normal window.

Developer tools shows this connection as blocked.

Disabling all extensions did not helped.

I'm now on LTE connection, 10/2.5Mbit 25ms, so it's rather not network related. And it works fine in other browsers.

Comment 9

[gwarser]

Attachment: net problem 1619061.zip

Screenshot of dev tools, about:support, har log, about:networking log.

Comment 10

[Ruby Clarke]

Maybe try hard refresh, and open a new browser?

Comment 11

[gwarser]

(In reply to Ruby Clarke from comment #10)

Maybe try hard refresh, and open a new browser?

Read bug 610357, this is "security feature" no one cares to fix completely.

I regularly see posts on r/firefox where users complain about this.

Comment 12

[Manuel Bucher [:manuel]]

We intent to improve the error handling and communication to the user. Showing a blank page is clearly misleading (similar to 4xx, 5xx errors)