User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1) Gecko/20061010 Firefox/2.0 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1) Gecko/20061010 Firefox/2.0 When moving quickly around web sites and clicking on items, such as scroll bars, before the previous command has fully refreshed the screen, Firefox 2 will occasionally hang. Task manager shows two firefox.exe tasks not responding when this happens, despite only one being visible. When it occurs, I usually have at least three tabs open. This behaviour is new to Firefox 2. Reproducible: Sometimes Steps to Reproduce: 1. Choose any site with many controls - for me it happens mostly with etrade.com.au (stock trading site) 2. Make many fast actions without waiting for refresh to complete 3. Watch it hang.
Did you also test this in Firefox's safe-mode to exclude extension problems, with a new profile or with a re-installation in a new empty directory?
(In reply to comment #1) > Did you also test this in Firefox's safe-mode to exclude extension problems, > with a new profile or with a re-installation in a new empty directory? > Sorry, I am not a Firefox techie. I don''t know what safe-mode is and its not in the supplied help. The only addons (is this an extension?) I am using are Tabbrowser, Google toolbar and Talkback (which BTW doesn't kick in when I kill the hung firefox.exe). Profiles are not in the help either. All the files in the installation directory are for the latest version, except for two files that are xml comments re updates. I am hoping that the appearance of the second instance of firefox.exe when it hangs will mean something to someone.
After some experimentation, I have discovered that IE6 behaves in exactly the same way. Therefore I assume its something to do with my internal wireless network, not firefox 2. I will close this bug as INVALID as it doesn't appear to be firefox2 (if I can, else please do so for me). Thx David
Status: UNCONFIRMED → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.