Closed Bug 580511 Opened 15 years ago Closed 11 years ago

firefox freezes up when i start browser except in safe mode. none of my toolbars work. help

Categories

(Firefox :: Extension Compatibility, defect)

3.6 Branch
x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: basicblackeagle, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.6) Gecko/20100625 Firefox/3.6.6 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.6) Gecko/20100625 Firefox/3.6.6 Warning: Expected ',' or '{' but found '*'. Ruleset ignored due to bad selector. Source File: http://wwwimages.adobe.com/www.adobe.com/lib/com.adobe/template/screen.css Line: 1987 bugzilla.mozilla.org : potentially vulnerable to CVE-2009-3555 Error: this._update is null Source File: file:///C:/Program%20Files/Mozilla%20Firefox/components/nsUpdateService.js Line: 2349 Reproducible: Always
If safe-mode works then you've got an incompatible add-on -- either you've disabled compatibility checking (unlikely) or one of the add-ons is lying about its compatibility range. The latter is especially likely if it was added by a 3rd party tool you installed, they apparently believe wishing makes it so. A malware add-on is also a possibility. The warnings you pasted above are not the source of your problem. The update service error could have bad effects (not getting updates?) but shouldn't be causing a browser freeze. You will need help from the forums or live chat at http://support.mozilla.com/ The best approach might be to first disable all your addons, and then turn them on one at a time (restarting in between each, a bit of a pain) until the problem happens. If you have a ton of addons you might try adding them in chunks, and then when you hit the freeze start turning them off one by one.
Group: core-security
Component: General → Extension Compatibility
QA Contact: general → extension.compatibility
Version: unspecified → 3.6 Branch
invalid, i.e. not a firefox bug, per comments
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.