This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

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

Disabling NoScript bricked my profile

  • 2 replies
  • 0 have this problem
  • 1 view
  • Last reply by Goldstein

more options

I previously had the NoScript extension. I disabled it in preferences and restarted Firefox. It seems like one of these moz-extension:// windows were open at the time, so when I try to launch Firefox, it tries to re-create moz-extensions:// windows and dies.

I can’t start Firefox. I can’t start Firefox in --safe-mode. I’m happy to provide any debug info needed.
I previously had the NoScript extension. I disabled it in preferences and restarted Firefox. It seems like one of these moz-extension:// windows were open at the time, so when I try to launch Firefox, it tries to re-create moz-extensions:// windows and dies. I can’t start Firefox. I can’t start Firefox in --safe-mode. I’m happy to provide any debug info needed.

Chosen solution

I actually remembered that I do daily backups and restored my profile. I’ll try to reproduce this and file a proper bug though. Thanks!

Read this answer in context 👍 0

All Replies (2)

more options

Do you need to retain tabs because if not then you can remove sessionstore.jsonlz4 in the Firefox profile folder to get a clean start ?

You can replace sessionCheckpoints.json in the profile folder with a sessionCheckpoints.json file that only contains "{}" (without the quotes) to get the about:sessionrestore page and select what to restore.

more options

Chosen Solution

I actually remembered that I do daily backups and restored my profile. I’ll try to reproduce this and file a proper bug though. Thanks!