1584804 - Random websites wont load at random times (not an internet issue, not an page issue - tested with other browsers)

Status: UNCONFIRMED

(Core :: Networking, defect, P3)

Description

[NeDamIme]

Attachment: Gecko profiler report during the ongoing event.

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:69.0) Gecko/20100101 Firefox/69.0

Steps to reproduce:

Normal browsing, either trying to open the page from the bookmark toolbar or by typing in the search box. Sometimes trying to middle-click on an index to open another instance of a page. It can work flawlessly for hours and then it starts acting all of the sudden so it's hard to reproduce. I found out that several people on a local IT forum have the same issue both on MacOS and Windows. Different AVs, different providers.

Actual results:

Whenever the issue occurs, the page will start loading but it won't load, for example the recorded event happened with Youtube, but it can happen with a random page. Even when i try to open another instance of the same website in a new tab the issue persists. When i try to open something else it loads flawlessly. Rarely it will happen with two different websites while the other ones are working as usual.

Expected results:

Normal loading of the opened website without long loading which brings me to the blank white page most of the times.

Comment 1

[Andrew Creskey [:acreskey]]

This is the attached profile:
https://perfht.ml/2ofcc5H

Comment 2

[Patricia Lawless]

NeDamime - could you provide a profile with all of the URLs and threads included?

Comment 3

[NeDamIme]

(In reply to Patricia Lawless from comment #2)

NeDamime - could you provide a profile with all of the URLs and threads included?

Hi Patricia,

i opened the same profile and ticked "Include hidden threads" and "Include resource URLs", hopefully that was what you're looking for.

https://perfht.ml/31LHoZ8

If you need a new recording with the Gecko Profiler with all threads included, please feel free to ask since i'm still not that experienced with the profiler and bug reporting so i'm not really sure if i'm doing the right thing.

Best regards.

Comment 4

[Honza Bambas (:mayhemer)]

Thanks for the report.

Instead of a profile, I'll ask for logs. When this happens, turn logging on in about:networking, for details see: https://developer.mozilla.org/en-US/docs/Mozilla/Debugging/HTTP_logging

Hopefully the cause will be visible if you start it after the problem has already manifested.

Thanks!

Comment 5

[NeDamIme]

(In reply to Honza Bambas (:mayhemer) from comment #4)

Thanks for the report.

Instead of a profile, I'll ask for logs. When this happens, turn logging on in about:networking, for details see: https://developer.mozilla.org/en-US/docs/Mozilla/Debugging/HTTP_logging

Hopefully the cause will be visible if you start it after the problem has already manifested.

Thanks!

Hello, sorry for the late reply but i had so much work to do so i couldn't be faster at replicating the issue. Here's the issue with Youtube again. I tried to open it and closed tabs until it finally loaded at the end. I also opened a lot of different sites, some are opening as usual and some of them are a little bit weird and show extended period of loading. Hopefully you'll see what's going on from the logs.

I had to upload it to WeTransfer, the original uncompressed file was 275MB, compressed it takes around 20MB.

Here's the link for the main and child log

https://we.tl/t-NDYvY4WKlV

Comment 6

[Honza Bambas (:mayhemer)]

Thanks!

We are not getting responses from the end server, the session [3] (started before the log was started) only actively serves pings in both directions, but doesn't serve responses. The request [0] is blocked on cache validation of [2] pending on request [1] (dispatched on [3]) for about 25 secs and then uses a new session (connection) because the session [3] was pruned for being idle too long in the mean time.

We deliberately don't implement response timeouts. One way to work around this (likely server issue) is to reload a loading page with Ctrl-F5 (not sure you can do this before the page starts loading, actually - which in this case does not...)

[0] nsHttpChannel @174ccffe000 created 2019-10-08 17:27:50.042 (log-main.3684)
[1] nsHttpChannel @174cd4ed000 created 2019-10-08 17:27:10.932 (log-main.3684)
[2] CacheEntry @174ccf56460 created 2019-10-08 17:27:10.945 (log-main.3684)
[3] Http2Session @174ccd53800 created 2019-10-08 17:26:08.373 (log-main.3684)

Comment 7

[NeDamIme]

Yeah, i started the log as soon as i noticed the page is not loading, that's why i tried to open several new tabs with Youtube just in case.

The thing that is bothering me is the fact that the same page loads instantly when the issue occurs and i try to load it in another browser, while it keeps loading in Firefox without any success.

It started happening somewhere around v69.0.1, i'm unsure about v69 since i don't recall this issue happened at that time.

Since i'm not really savvy with bug reporting, in simple words, can this issue be solved on your end in future updates?

Comment 8

[NeDamIme]

(In reply to Honza Bambas (:mayhemer) from comment #6)

Thanks!

We are not getting responses from the end server, the session [3] (started before the log was started) only actively serves pings in both directions, but doesn't serve responses. The request [0] is blocked on cache validation of [2] pending on request [1] (dispatched on [3]) for about 25 secs and then uses a new session (connection) because the session [3] was pruned for being idle too long in the mean time.

We deliberately don't implement response timeouts. One way to work around this (likely server issue) is to reload a loading page with Ctrl-F5 (not sure you can do this before the page starts loading, actually - which in this case does not...)

[0] nsHttpChannel @174ccffe000 created 2019-10-08 17:27:50.042 (log-main.3684)
[1] nsHttpChannel @174cd4ed000 created 2019-10-08 17:27:10.932 (log-main.3684)
[2] CacheEntry @174ccf56460 created 2019-10-08 17:27:10.945 (log-main.3684)
[3] Http2Session @174ccd53800 created 2019-10-08 17:26:08.373 (log-main.3684)

Yeah, i started the log as soon as i noticed the page is not loading, that's why i tried to open several new tabs with Youtube just in case.

The thing that is bothering me is the fact that the same page loads instantly when the issue occurs and i try to load it in another browser, while it keeps loading in Firefox without any success.

It started happening somewhere around v69.0.1, i'm unsure about v69 since i don't recall this issue happened at that time.

Since i'm not really savvy with bug reporting, in simple words, can this issue be solved on your end in future updates?

Comment 9

[Honza Bambas (:mayhemer)]

I am not sure we can do anything w/o further data. It seems the h2 session simply dies/gets stuck on the remote peer. Adding Dragana for any thoughts. We simply may keep the h2 session excessively long or do something the end server doesn't like and doesn't close the connection either.

Opening a new browser obviously creates a new h2 session. Ctrl-F5 in the running Firefox will also create a new h2 session. Going online and offline from the menu (flip twice File / Work Offline) will help as well by closing all existing connections.

Great would be to run logging all the time with added (or preserved, if you go by the directions) rotate:200 setting, using command line arguments or environment variables. That will capture more logging history before the problem has happened and maybe reveal something; ASAP you reproduce, close Firefox to save as much of the logs.

Comment 10

[Honza Bambas (:mayhemer)]

P3 for not enough info to act.

Comment 11

[kolos2020]

I have the same problem when opening this page https://tabaki.store/pod sometimes the page opens normally and sometimes it doesn't load for hours.

Comment 12

[masghar234]

I think there is no matter how many cute characters that browsers plaster over their error pages, a web page going down is still a source of frustration. If you're trying to visit your favorite site only to be greeted by "This site can't be reached," "The connection has timed out," or the ever-cryptic 404 error when i visit https://crack6.com , here are a few things to try.

Once you've narrowed down the problem to a single site (or a few sites), check to see if those sites are down for everyone or just you. The aptly named downforeveryoneorjustme.com is perfect for this, allowing you to type in any URL to see if the site is up for other people.

https://bit.ly/3xF7XAb