User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.5; en-US; rv:184.108.40.206) Gecko/2008102920 Firefox/3.0.4 Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.5; en-US; rv:220.127.116.11) Gecko/2008102920 Firefox/3.0.4 When I am moving back and forth from one program to another, Firefox seems to take up to 2 minutes doing something either the programs main cache or distributing memory before I can actually use the program. Before 3 updates ago, it didn't do this, but since this new generation, it does it all the time. In comparison, Safari doesn't do this and can be used in a matter of seconds not minutes. Have you changed how the program uses memory or caches itself before operation? Reproducible: Always Steps to Reproduce: 1.Have a couple of programs open. I have Indesign and Adobe Reader 2. Switch from program to program and try to do anything. 3. One of the websites I was on was istockphotos.com and doing searches for images Actual Results: Slow performance and usability. Must wait minutes until browser is ready for use. Expected Results: Switching from program to Firefox, although I realize shouldn't be instantaneous, but should be ready to go at least in 10 to 20 seconds. Safari is faster.
Thank you for this report. However, in order to make it more useful, please follow the steps found at http://new.quality.mozilla.org/bug-writing-guidelines and report back with your results.
This is a mass search for Firefox General bugs filed against version 3.0 that are UNCO and have not been changed for 200 days. Reporter, please update to Firefox 3.6.10 or alter. Firefox 3.0 is no longer supported and is no longer receiving updates. After you update, please create a fresh profile, http://support.mozilla.com/kb/managing+profiles, and test to see if your bug still exists. If you still the bug, then please post a comment with the version you tested against, and the problem. If the issue is no longer there, 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.