Where did you install Firefox from? Help Mozilla uncover 3rd party websites that offer problematic Firefox installation by taking part in our campaign. There will be swag, and you'll be featured in our blog if you manage to report at least 10 valid reports!

Mozilla サポートの検索

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

このスレッドはアーカイブに保管されました。 必要であれば新たに質問してください。

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

  • 2 件の返信
  • 1 人がこの問題に困っています
  • 1 回表示
  • 最後の返信者: 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.

選ばれた解決策

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).

この回答をすべて読む 👍 0

すべての返信 (2)

more options

選ばれた解決策

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).

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.