Bugzilla

(In reply to alex_mayorga from comment #38)
> but it seemed to never finish loading (there's just a dot bouncing left and right where the tab icon should have been).
> 
> I captured this profile:
> https://share.firefox.dev/3gQd498

Thanks!

So in that profile, the biggest thing I see are some network requests to URLs on https://signaler-pa.clients6.google.com/ that are taking a loooong time for responses. You can seem them in the marker-chart at the bottom here -- the first one apparently was a request from before you started profiling, and it took 61 seconds before it got a response (based on "HTTP Response: 61,553ms" when you hover that bar); and the last one was still un-answered ("Status: waiting for response") at the end of your profile (after it had been waiting for ~16 seconds).

I'm assuming those requests are what the pageload is blocked on, which is why it never finishes loading.

This seems pretty-bad, but also seems explainable by network issues upstream of you.  Could you check if it's still not-finishing-loading, and it you see that same outcome in other browsers as well?

(In reply to alex_mayorga from comment #38)
> but it seemed to never finish loading (there's just a dot bouncing left and right where the tab icon should have been).
> 
> I captured this profile:
> https://share.firefox.dev/3gQd498

Thanks!

So in that profile, the biggest thing I see are some network requests to URLs on https://signaler-pa.clients6.google.com/ that are taking a loooong time for responses. You can seem them in the marker-chart at the bottom here -- the first one apparently was a request from before you started profiling, and it took 61 seconds before it got a response (based on "HTTP Response: 61,553ms" when you hover that bar); and the last one was still un-answered ("Status: waiting for response") at the end of your profile (after it had been waiting for ~16 seconds).

I'm assuming those requests are what the pageload is blocked on, which is why it never finishes loading.

This seems pretty-bad, but also seems explainable by network issues upstream of you.  Could you check if it's still not-finishing-loading (i.e. maybe the network issues went away, due to a router reboot in some datacenter)?  And if it's still happening, could you see if it's not-finishing-loading in other browsers as well?