Problem:
After opening the Tor Browser and typing in facebook.com, page loading hangs, status bar showing "Waiting for static.xx.fbcdn.net"
HTTP GET requests for small images from static.xx.fbcdn.net stall in the "Blocked" state for minutes - viewed in Developer tools / Network / request / Timing (see attached screenshot Step2.png).
When a different website is opened in a new tab, HTTP requests continue loading successfully - seems to be some livelock within the browser.
This is not a network issue, connectivity in the browser works fine, also verifed without a SOCKS proxy (direct connection without Tor).
Reproducibility: nearly 100%
Environment:
Windows 10 Pro, 64bit
Tor Browser 7.5.3 for Windows, english
Tor Browser 8.0a5 for Windows, english
Trac: Username: uzi
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Child items 0
Show closed items
No child items are currently assigned. Use child items to break down this issue into smaller parts.
Linked items 0
Link issues together to show that they're related.
Learn more.
Hm, I wonder what's up here. Do you have some antivirus/firewall tool that could be interfering? If so, could you uninstall it for a test (disabling is often not enough) and see if that fixes your issue?
Trac: Status: new to needs_information Keywords: N/Adeleted, tbb-usability-website added
Tried on a third machine, Win 7, another internet connection, antivirus uninstalled, no firewall - same behavior.
Did you try with https://facebookcorewwwi.onion/?
I wonder whether this is a duplicate of/related to #21924 (moved), gk says there:
This change e.g. if I go to Trac in a new tab. Suddenly the icon on the former tab stops spinning and all is fine. This happens at least with a 64bit Linux.
(Sorry for the vague bug report :) )
Which seems to be the same case here (except the bug report is more precise :) ).
Maybe bugs like these can be simulated with a firejail --bandwidth=torbrowser set eth0 5 6 or worse, I don't know, but it seems like this is due to static.xx.fbcdn.net being overloaded by exits, and it took time to load up and something weird happened. If I recall trac.tp.o had also some overloading issues at the time, maybe that's why gk was experiencing a similar bug at the time.
Maybe bugs like these can be simulated with a firejail --bandwidth=torbrowser set eth0 5 6 or worse, I don't know, but it seems like this is due to static.xx.fbcdn.net being overloaded by exits, and it took time to load up and something weird happened. If I recall trac.tp.o had also some overloading issues at the time, maybe that's why gk was experiencing a similar bug at the time.
Good idea, but I think it's something different here. OP: does it help if you flip network.http.spdy.enabled and network.http.spdy.enabled.http2 to true (just for testing purposes)?
OP: does it help if you flip network.http.spdy.enabled and network.http.spdy.enabled.http2 to true (just for testing purposes)?
It indeed does help - facebook loads instantly.
Important remark reiterated: the problem also happens when not connecting via Tor (reconfigured Tor Browser to just use a plain proxy or no proxy at all).
OP: does it help if you flip network.http.spdy.enabled and network.http.spdy.enabled.http2 to true (just for testing purposes)?
It indeed does help - facebook loads instantly.
Important remark reiterated: the problem also happens when not connecting via Tor (reconfigured Tor Browser to just use a plain proxy or no proxy at all).
Yes. It's not Tor-related but related to the above mentioned browser settings which are still active even if you configure a different proxy or none at all. We need #14952 (moved) sorted out first, to solve this problem which is supposed to happen soon.