User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9) Gecko/2008052906 Firefox/3.0 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9) Gecko/2008052906 Firefox/3.0 When using firefox 3 on XP (SP3, all updates) and a dialup modem connection web browsing is terribly slow. In the network communication, you see that transfer count gets slow and slower and pauses. Error count runs up, it seems like the serial modem line is bad. But using IE7 on the same machine goes fast without errors. The serial line has no problem. A downgrade to Firefox 2.0.14 also solved the problem, this version runs smooth. Reproducible: Always Steps to Reproduce: 1. Use 56k modem, dialup connection 2. try the example url Actual Results: I tried it on two machines, a Pentium III-800 PC and a Pentium-III 1000 Laptop with same results. Problem is not limited to the given url, it happens generally. Expected Results: FF3 should behave as smooth as FF2 on dialup connections
Firefox is using only the OS TCP/IP connection and doesn't know anything about the serial com port. If you get errors there then it's not Firefox fault (it doesn't matter if you get this only with Firefox). Firefox3 could be slow on dialup because it downloads the Phishing and malware sites in the background. Deactivating this feature in the options should help but firefox will you not warn anymore.
This is a mass search for bugs that are in the Firefox General component, are UNCO, and have not been changed for 800 days and have an unspecified version. Reporter, can you please update to Firefox 3.6.10, create a fresh profile, http://support.mozilla.com/en-US/kb/managing+profiles, and test again. If you still see the bug, please update this bug. If the issue is gone, please set the resolution to RESOLVED > WORKSFORME.
No reply from reporter, INCOMPLETE. Please retest with Firefox 3.6.12 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.