搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

Learn More

Extensions and Search Not Working

  • 1 回覆
  • 1 有這個問題
  • 18 次檢視
  • 最近回覆由 Goober4473

more options

As of today, all of my Firefox extensions have stopped working and all of the search engines have been removed from the Default Search Engines menu.

I've tried everything I can find for either problem, but nothing has worked and they seem related?

Extensions:

  • Reinstalling extensions did not work. They're still listed as enabled on my extensions settings page.
  • I'm not in private browsing mode and my extensions are set to be usable in private mode anyways.
  • Extension icons don't appear anywhere in the customizing menu for the toolbar, including the overflow menu.

Search:

  • Deleting the search.json.mozlz4 file did not work; it didn't create a new file.
  • "Restore Default Search Engines" button in search options is grayed out.

Both:

  • Reinstalling Firefox did not work.

I have no idea what to do at this point.

As of today, all of my Firefox extensions have stopped working and all of the search engines have been removed from the Default Search Engines menu. I've tried everything I can find for either problem, but nothing has worked and they seem related? Extensions: * Reinstalling extensions did not work. They're still listed as enabled on my extensions settings page. * I'm not in private browsing mode and my extensions are set to be usable in private mode anyways. * Extension icons don't appear anywhere in the customizing menu for the toolbar, including the overflow menu. Search: * Deleting the search.json.mozlz4 file did not work; it didn't create a new file. * "Restore Default Search Engines" button in search options is grayed out. Both: * Reinstalling Firefox did not work. I have no idea what to do at this point.

被選擇的解決方法

It seems like messing with the values for cache size and mas processor use was causing this. Not sure which one did it, but reverting them all fixed it.

從原來的回覆中察看解決方案 👍 0

所有回覆 (1)

more options

選擇的解決方法

It seems like messing with the values for cache size and mas processor use was causing this. Not sure which one did it, but reverting them all fixed it.