NoScript randomly resets individual tab settings
Posted: Sat Mar 28, 2020 6:27 pm
Hi,
I am running NoScript 11.0.23 on Firefox firefox-74.0_2 on FreeBSD 12.1-RELEASE. I am seeing a couple of bothersome behaviors.
1. On random tabs, NoScript will reset it's settings, e.g. turning "temp trusted" back to default (untrusted). And it does this without changing the state in the pulldown that appears when you click on the item. Sometimes, I can click the master reload (green circular arrow in the top row of the pulldown), which usually works, though on more than one occasion didn't, requiring me to restart firefox.
2. I have encountered this as well. I click reload on a tab (for instance to update a news tab), and it will never reload. It will do this on all tabs, master reload does not work, and I have to restart firefox.
I have been running rosetta@home to donate cycles to the covid-19 research efforts, and the problem with noscript seems to be exacerbated when there is memory pressure, but both behaviors still occur regularly when the system is in it's steady state.
Can anyone suggest anything I can do to fix this?
I am running NoScript 11.0.23 on Firefox firefox-74.0_2 on FreeBSD 12.1-RELEASE. I am seeing a couple of bothersome behaviors.
1. On random tabs, NoScript will reset it's settings, e.g. turning "temp trusted" back to default (untrusted). And it does this without changing the state in the pulldown that appears when you click on the item. Sometimes, I can click the master reload (green circular arrow in the top row of the pulldown), which usually works, though on more than one occasion didn't, requiring me to restart firefox.
2. I have encountered this as well. I click reload on a tab (for instance to update a news tab), and it will never reload. It will do this on all tabs, master reload does not work, and I have to restart firefox.
I have been running rosetta@home to donate cycles to the covid-19 research efforts, and the problem with noscript seems to be exacerbated when there is memory pressure, but both behaviors still occur regularly when the system is in it's steady state.
Can anyone suggest anything I can do to fix this?