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!

Поиск в Поддержке

Избегайте мошенников, выдающих себя за службу поддержки. Мы никогда не попросим вас позвонить, отправить текстовое сообщение или поделиться личной информацией. Сообщайте о подозрительной активности, используя функцию «Пожаловаться».

Подробнее

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.