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

Echekwara usoro a. Biko jụọ ajụjụ ọhụrụ ma ọ bụrụ na ị chọrọ enyemaka.

Firefox 72 causes Add-Ons to stop running while still enabled

  • 2
  • 2
  • 6 views
  • Nzaghachi ikpeazụ nke cor-el

aimmyarrowshigh
aimmyarrowshigh
more options

Firefox 72.0.1 and 72.0.2 have the same issue, so the latest release did not solve it. My add-ons all stop working, or seem to time out somehow, while still showing as enabled. Removing and then "Undo Remove" of the add-ons restarts this new timeout clock/fixes the problem, but it's extremely frustrating and ineffective.

  • This did not happen prior to 72.0.1.
  • The add-ons do retain my settings even while timed out/stopped/somehow broken, so they are not actually disabled during these outages.
  • This affects all add-ons, so it is not a problem with any one specific add-on.
Firefox 72.0.1 and 72.0.2 have the same issue, so the latest release did not solve it. My add-ons all stop working, or seem to time out somehow, while still showing as enabled. Removing and then "Undo Remove" of the add-ons restarts this new timeout clock/fixes the problem, but it's extremely frustrating and ineffective. * This did not happen prior to 72.0.1. * The add-ons do retain my settings even while timed out/stopped/somehow broken, so they are not actually disabled during these outages. * This affects all add-ons, so it is not a problem with any one specific add-on.

All Replies (2)

Eve
Eve
more options

Might be worth submitting as a bug, does the same thing happen in Developer (73) or Nightly (74)? https://www.mozilla.org/en-US/firefox/developer/ https://www.mozilla.org/en-US/firefox/channel/desktop/#nightly

Let me know

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

What security software do you have ?

This can be caused by a problem with the extensions registry files in the profile folder.

If it happens again:

Try to to reset the extensions registry and rename extensions.json (extensionsOLD.json) and rename/remove previously used extensions files like extensions.ini and extensions.sqlite when present and rename/remove compatibility.ini in the Firefox profile folder to invalidate caches with Firefox closed.

You can use the button on the "Help -> Troubleshooting Information" (about:support) page to go to the current Firefox profile folder or use the about:profiles page.

New files will be created when required.

See "corrupt extension files":