Works for me. Does that problem persist if you donwload a clean, new version? If so, which version is affected? Does it happen regularly? Do you have special NoScript settings or are you using the default ones? Re: your version, see my comment in #11450 (closed).
As far as I remember, NoScript was last installed fresh, then disabled (but not uninstalled), and certainly it has been disabled for a long time. It is not enabled and was not when I first got the error (I use a different toggle that blocks all java, I don't like NoScript).
I tend to install on top of previous installs. I know this can lead to bugs (peripheral issue: if advice is available regarding how to update clean without having to reinstall all plugins and re-set all settings, it would be appreciated)
I'll post again when I've run a fresh instance with NoScript disabled.
Unpacked fresh instance to new random location, ran it, went into addons, disabled NoScript, hit restart, when browser reappeared hit New Identity, same error.
Did not install any addons or plugins or alter any settings other than to disable NoScript.
The problem is disabling NoScript as we are currently using a part of its code to clear temporary NoScript permissions. We should be smarter here and check whether NoScript is enabled at all (and only show the alert in this case!? or not calling eraseTemp() in the first place?). If it is disabled then there should not be any temporary NoScript permission active, and hence no need to clear the perms/show the alert.
I did, I added an alert before and inside the if. The first one gets called always (with NoScript enabled and disabled), the second one only if NoScript is enabled.