User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:22.214.171.124) Gecko/20071025 Firefox/126.96.36.199 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:188.8.131.52) Gecko/20071025 Firefox/184.108.40.206 In Tools, Options, Privacy, Cookies section, clicking on "Exceptions" button causes Firefox to stall. Eventually a spurious "Unresponsive script" window appears, clicking on "Continue" has no effect. Eventually Firefox becomes responsive again, but list of exceptions never appears. Reproducible: Always Steps to Reproduce: 1. Go to any website. 2. Click on Tools, Options, Privacy, Exceptions 3. Actual Results: Firefox freezes, eventually a spurious "Unresponsive script" window appears. Expected Results: List of websites with allowed cookies (or disallowed, doesn't matter) should appear.
does this occur with a new profile? (see http://kb.mozillazine.org/Profile_Manager#Creating_a_new_profile if you don't know how to create one.) if it doesn't, how large is your hostperm.1 file in your original profile directory? if it doesn't contain any information you'd like to keep private, can you attach it to this bug? (you can open the file in a regular text editor, like notepad, to find out.)
This bug was reported on Firefox 2.x or older, which is no longer supported and will not be receiving any more updates. I strongly suggest that you update to Firefox 3.6.3 or later, update your plugins (flash, adobe, etc.), and retest in a new profile. If you still see the issue with the updated Firefox, please post here. Otherwise, please close as RESOLVED > WORKSFORME http://www.mozilla.com http://support.mozilla.com/kb/Managing+profiles http://support.mozilla.com/kb/Safe+mode
No reply, INCOMPLETE. Please retest with Firefox 3.6.x 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.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.