We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

This thread was archived. Please ask a new question if you need help.

Error opening FF 8 "TypeError: Components.classes[cid] is unidefined"

  • 2 replies
  • 1 has this problem
  • 1 view
  • Last reply by petero

petero
petero
more options

I've just upgraded from FF 3.6 to FF 8. Every time I open FF 8, I get this error dialog box:

[JavaScript Application]

TypeError: Components.classes[cid] is unidefined

I just performed the upgrade, so haven't used FF 8 enough yet to know if the error causes any problems.

Thanks for your assistance.

I've just upgraded from FF 3.6 to FF 8. Every time I open FF 8, I get this error dialog box: [JavaScript Application] TypeError: Components.classes[cid] is unidefined I just performed the upgrade, so haven't used FF 8 enough yet to know if the error causes any problems. Thanks for your assistance.

Chosen solution

That issue can be caused by an extension that isn't working properly.

Start Firefox in Diagnose Firefox issues using Troubleshoot Mode to check if one of the extensions or if hardware acceleration is causing the problem (switch to the DEFAULT theme: Firefox (Tools) > Add-ons > Appearance/Themes).

Read this answer in context 👍 0

All Replies (2)

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

Chosen Solution

That issue can be caused by an extension that isn't working properly.

Start Firefox in Diagnose Firefox issues using Troubleshoot Mode to check if one of the extensions or if hardware acceleration is causing the problem (switch to the DEFAULT theme: Firefox (Tools) > Add-ons > Appearance/Themes).

petero
petero Question owner
more options

Thanks, cor-el! FF started without the error in Safe Mode, so I disabled all the add-ons that had compatibility warnings, then enabled them one by one. It was AVG Safe Search that was causing the error.