Closed Bug 335312 Opened 19 years ago Closed 19 years ago

An increasing amount of websites won't load in Firefox

Categories

(Firefox :: General, defect)

Product:
Firefox
Component:
General
Platform:
x86
Windows XP
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: dylananglada, Unassigned)

References

(
URL
)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.2) Gecko/20060308 Firefox/1.5.0.2 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.2) Gecko/20060308 Firefox/1.5.0.2 Lately (beginning around April 15 or so), an increasing amount of websites have been loading slowly in Firefox. Before I go any further, let me clear up that I HAVE tried running Firefox in Safe Mode, and still had the same result. Below is a list of some sites which I have found have had decreased loading speed in Firefox: http://www.google.com http://www.gmail.com http://www.tugzip.com http://www.sectionz.com http://www.sectionzmusic.com http://www.sectionzrecords.com http://www.alta-vista.com Reproducible: Always Steps to Reproduce: 1. Open Firefox 2. Visit any of the sites I listed Actual Results: Some sites did not load at all (e.g. tugzip, gmail, google, alta-vista), while the others were extremely sluggish Expected Results: Sites should load normally, or loaded at a normal 11.0 mbps speed.
Google and Gmail have started working again. At least, for me
Google and GMail have stopped again. I tried all that stuff above. Nothing worked. However, when I cleared all the cookies, they started working again for a short time. I scanned for adware, viruses, and spyware, but found nothing.
I took the SSL test, and passed. Perhaps it's a probelm with Google?
Now they're working again suddenly.
Okay, I left the Google homepage on the screen for about 5 minutes. Suddenly, the "Problem loading page" screen appeared, when I didn't click anything. I didn't even touch the computer. The error message said: The connection has timed out ---------------------------- The server at www.google.com is taking too long to respond. The exact address of the page I was on is: http://www.google.com/ig?hl=en
Here is a list of all of the stuff about my Firefox setup that I thought might be of even the slightest help in determining, and hopefully fixing, the problem(s). ---------------------------------------------------------------------------------- Extensions I have installed as of 6:30PM (GMT -05:00), on April 25, 2006: - Forecastfox Enhanced 0.8.5.2 - PDF Download 0.6 - Disable Target For Downloads 1.0.1 - Download Manager Tweak 0.7.1 - SiteAdvisor Firefox Extension 20.0 - Google Toolbar for Firefox 2.0.20060404 - Adblock v.5 d3 *nightly 42 - Adblock Filterset.G Updater 0.3.0.3 ---------------------------------------------------------------------------------- Security-Related Programs I have installed as of 6:30PM (GMT -05:00) on April 25, 2006: - McAfee Security Center * McAfee VirusScan * McAfee Privacy Service * McAfee Personal Firewall Plus - Ad-Aware SE Personal 6 - Spybot Search & Destroy 1.4.0.3 - Spyware Blaster 3.5.0.1 ------------------------------------------------------------------------------- Plug-ins I have installed for Firefox as of 6:31 PM (GMT -05:00): - Adobe Flash Player 8.5 Beta - Macromedia Shockwave Player 10.1.1.016 - Macromedia Authorware Player 2004,0,0,73 -------------------------------------------------------------------------------
Now http://www.myspace.com is acting weird. The Flash audio players are extremely sluggish. Also, I uninstalled Adblock, and installed AdBlock Plus 0.7. I also installed the Noia 2.0 (eXtreme) 3.12 theme for Firefox.
Ever since updating to version 1.5.0.3, the sites are loading fine.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Status: RESOLVED → UNCONFIRMED
Resolution: FIXED → ---
Only bugs with code that gets checked in get resolved as fixed. Resolving bug as works for me.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago → 19 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.