Closed Bug 660093 Opened 14 years ago Closed 14 years ago

Slow script warning when opening about:permissions

Categories

(Firefox :: Settings UI, defect)

x86
Windows XP
defect
Not set
critical

Tracking

()

RESOLVED INVALID

People

(Reporter: guijoselito, Unassigned)

Details

(Whiteboard: [INVALID?])

User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:7.0a1) Gecko/20110526 Firefox/7.0a1 Build Identifier: Mozilla/5.0 (Windows NT 5.1; rv:7.0a1) Gecko/20110526 Firefox/7.0a1 In Portuguese: "Um script desta página pode estar em execução ou parado de responder. Você pode interrompê-lo agora ou continuar para verificar se ele termina a execução. Script: chrome://browser/content/preferences/aboutPermissions.js:510" There is a lot of websites in the list, that I've never visited. I suspect it's something that Spybot - Seach & Destroy does, or Advanced System Care 4, about protecting the user from malicious sites, that includes these entries. And the loading of thousands of websites give me the warning. (I'm on a very old system - Pentium 4, 3GHz) Could the Firefox Team find out which program is, and find out if it's something that can be fixed on your side, or contact the other developers to fix it on their end? Reproducible: Always
How about excluding the Firefox Installation Directory from the Scanning Process of those Programs (if possible)? Due to the Nature Firefox Browser is built upon - JS, HTML, XUL Files those Programs scan - I doubt there can anything done about the Issue from this Side for Prevention.
Whiteboard: [INVALID?]
So, I undid Spybot's immunization, and the problem is gone. I think Spybot is a popular software, lots of people is going to find the same problem. Can you guys report the problem to Spybot Team? I should say that I still have some weird entries on the Permissions Manager, so other program(s) do the same, but Spybot has the largest list of malicious websites.
You could report it to e.g. their Forums: http://forums.spybot.info/forumdisplay.php?f=3
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.