"Policy is not defined" error

[Whatever]

With NoScript 2.6.3, when visiting any Twitch.tv stream, the chat stops working after a while, and my error console is spammed with the following error:

Error: Policy is not defined
Source: jar:file:///.../extensions/%7B73a6fe31-595d-460b-a920-fcc0f8843232%7D.xpi!/components/noscriptService.js
Line: 1384

I guess

Code: Select all

Policy

in that line should be

Code: Select all

PolicyState

?

[aloishammer]

Confirmed.

Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0

(Firefox 18b4)

ETA: The Mycroft project is broken for me. Attempting to install plugins leads to an error telling me JS isn't enabled. It is. Haven't changed any rules regarding Mycroft in a long time.

[Thrawn]

The Mycroft project is broken for me. Attempting to install plugins leads to an error telling me JS isn't enabled. It is. Haven't changed any rules regarding Mycroft in a long time.

OK, but has the Mycroft project changed? Which sites are being blocked when you go there?

[aloishammer]

OK, but has the Mycroft project changed? Which sites are being blocked when you go there?

Nothing has changed that I can see. I'm usually on the site about once a month. The only thing that's different is I'm using a more recent (latest) dev build of NoScript, and I'm getting a pile of NoScript-related errors (noscriptService.js) in the Error Console. I have to assume it's NoScript that has the problem, and not Firefox nor the Mycroft site. And I'm not blocking anything at all. All page elements are being served from mozdev.org (or, I assume, mycroft.mozdev.org specifically).

I do use ABE with the default SYSTEM rule set:

Code: Select all

# Prevent Internet sites from requesting LAN resources.
Site LOCAL
Accept from LOCAL
Deny

There are no errors being reported by NoScript itself. There are no ABE errors. There are no ClearClick warnings. There are no XSS warnings. All I have to go on is Firefox horking an error every few seconds on noscriptService.js. Disabling the obvious content blockers (ABP + Ghostery) changes nothing.

I can visit the same results page in Chrome (wherein I am also using the Ghostery and AdBlock plugins, with the same block lists), plus default-deny JS. (JS is enabled for [.*].mozdev.org, same as in NoScript on Firefox.)

When I attempt to add the same—or any—search engine in Chrome, Mycroft happily serves up search plugin information, and I can add the engine in Chrome. Opera also experiences no problems on the Mycroft site, also using ABP and Ghostery.

[aloishammer]

The Mycroft project is broken for me. Attempting to install plugins leads to an error telling me JS isn't enabled. It is. Haven't changed any rules regarding Mycroft in a long time.

OK, but has the Mycroft project changed? Which sites are being blocked when you go there?

One other thing: after installing the latest dev build of NoScript, it looks like Firefox may be experiencing some sort of resource leak. If Firefox is left running around 24hrs with nominal usage, it suddenly starts loading pages / page elements very, very, VERY slowly, as if I were experiencing massive packet loss; which I'm not. A soft-restart of Firefox fixes it.

[aloishammer]

Not resolved as of 2.6.4rc2.

[aloishammer]

With NoScript 2.6.3, when visiting any Twitch.tv stream, the chat stops working after a while, and my error console is spammed with the following error:

Error: Policy is not defined
Source: jar:file:///.../extensions/%7B73a6fe31-595d-460b-a920-fcc0f8843232%7D.xpi!/components/noscriptService.js
Line: 1384

I guess

Code: Select all

Policy

in that line should be

Code: Select all

PolicyState

?

Whatever, it looks like that was a good guess. Code modified, extension repacked. No errors reported in the console now. Interestingly, though, this did not fix my problem with the Mycroft project. It's possible this is merely turning one code error into another, or masking the original error. Still, less console spam seems like an improvement. New code:

Code: Select all

  earlyHttpObserver: {
    observe: function(channel, topic, data) {
      PolicyState.attach(channel);
    }
  },

[aloishammer]

Last entry, I hope: Mycroft Project site failure was not related to this NoScript bug:

Code: Select all

apt-get purge xul-ext-unity xul-ext-websites-integration

I assume it was xul-ext-unity. Bug has been reported to Ubuntu team.

[aloishammer]

Not resolved as of Not resolved as of 2.6.4.2rc1. This should be an easy fix.

[Giorgio Maone]

Sorry, I had completely missed this thread.
Fixed in latest development build 2.6.4.2rc2, thank you.

[aloishammer]

Sorry, I had completely missed this thread.
Fixed in latest development build 2.6.4.2rc2, thank you.

Much appreciated!