Firefox hangs on Websites (example: g2play.net)
Hi,
whenever i start a fresh Firefox Process and open Websites (example: g2play.net), Firefox will freeze for around 3 Minutes before the Website loads. This happens on a bunch of different Websites. Different browsers work fine (tried IE10).
What i have tried to fix this issue: - Disable all Addons - Disable Javascript - Start in Safe Mode - Clear all Files (Cache, Offline Data, everything) - Completely remove and install Firefox new - Create a new Windows user - Update all Drivers - Closing all the background programs i could close
Nothing fixed my Problem so far.
Computer Specs: Windows 7 64 bit SP1 updated to the newest versions AMD Phenom II x6 1100T - 6 core proccesor running at 3,30 GHZ noname 8 GB DDR 3 RAM ATI Radeon HD 5750 noname 2 TB Harddrive
Programs running in the background: Steam, Thunderbird, Avast, Winamp, Piclair, Brother ControlCenter3, Brother Status Monitor, Razer Lachesis 5600, AMD Vision Engine Control Center
I think (im not 100% sure on this) that the problem first appeared with Firefox 20.0.1. Also it only happens when loading that website for the first time, once its cached it doesn't hang anymore (i have my firefox set to clear the cache everytime the browser exits).
edit: it's not my connection, neither my DNS Server. I got a 100mbit connection running and i have tried to access the website directly over the IP but the problem still remains.
vDrag0n மூலமாக திருத்தப்பட்டது
தீர்வு தேர்ந்தெடுக்கப்பட்டது
I couldn't understand why about:downthemall, an internal page, would freeze, but I see that the images are populated from downthemall.net and it imports fonts from Google. surrenderat20 also uses Google fonts. g2play hosts its own custom fonts. Is that a pattern?
In case downloadable fonts are an issue, you can disable that feature in about:config by toggling this preference:
gfx.downloadable_fonts.enabledRead this answer in context 👍 6
All Replies (2)
During these freezes I have noticed that the loading webpage often has the word "static" in its name. Is that helpful at all in resolving this?
Hi iantwebb, I've seen "static" used with files being loaded from a content distribution network rather than the main server. (Of course, that may or may not be the case with the page(s) giving you problems.)
I assume you've done the standard troubleshooting for the problem site(s), e.g., clearing cache and site-specific cookies, trying Firefox's Safe Mode?