1001968 - NoScript hangs on options menu

Status: RESOLVED INCOMPLETE

(Toolkit :: General, defect)

Description

[JosephRPlante]

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Firefox/31.0 (Beta/Release)
Build ID: 20140426221705

Steps to reproduce:

Simply load up NoScript's options and it hangs. I'm using Nightly on Windows 7 x64. I'm not sure if it's a Firefox or NoScript (Happens in regular FF on me as well)



Actual results:

It hung and then says there's an unresponsive script on listbox.xml. Unfortunately, if you stop script, it'll hang again and repeats infinitely

mozilla-source\mozilla-central\toolkit\content\widgets\listbox.xml

var parent = this.parentNode;

of function

     <property name="control">
        <getter><![CDATA[
          var parent = this.parentNode;
          while (parent) {
            if (parent instanceof Components.interfaces.nsIDOMXULSelectControlElement)
              return parent;
            parent = parent.parentNode;
          }
          return null;
        ]]></getter>
      </property>



Expected results:

No crash

Comment 1

[JosephRPlante]

Hm... I was able to fix the crashing by going to about:config and resetting all values. Still, weird

Comment 2

[JosephRPlante]

Another thought: the error points to listbox.xml, and one of those about:config entries had a ;-seperated list. The list stuck around even after noscript got uninstalled

Comment 3

[JosephRPlante]

Attachment: The about:config leftovers from after uninstalling NoScript. I think this line might be the cause

Comment 4

[JosephRPlante]

capability.policy.maonoscript.sites might be the entry

Comment 5

[Paul Silaghi, QA [:pauly]]

(In reply to JosephRPlante from comment #0)
> Simply load up NoScript's options and it hangs. 
Couldn't reproduce in Nightly 31.0a1 (2014-04-28), Win 7 x64 with NoScript Security Suite 2.6.8.20.
Please try on a new, empty profile:
http://support.mozilla.org/en-US/kb/Managing-profiles#w_starting-the-profile-manager

Comment 6

[JosephRPlante]

Clearing capability.policy.maonoscript.sites in about:config fixed it

Comment 7

[JosephRPlante]

Okay, that's not entirely correct, I'll admit: clearing all noscript variables in about:config fixed it (thanks to a poster on the Interwebs for the suggestion), but I feel that capability.policy.maonoscript.sites might be a possible cause

Comment 8

[Paul Silaghi, QA [:pauly]]

(In reply to Paul Silaghi, QA [:pauly] from comment #5)
> Please try on a new, empty profile:
I meant you should try to install NoScript on a clean profile
(In reply to JosephRPlante from comment #6)
> Clearing capability.policy.maonoscript.sites in about:config fixed it
I don't see any hang/crash without clearing anything

Comment 9

[Francesca Ciceri [:madamezou]]

Hi, 

I wasn't able to reproduce it on Nightly 32.0a1 (2014-05-29), Debian Linux x86_64 with No Script Security Suite 2.6.8.26.

With two WFM on two different platforms, I'd be tempted to close it but first:

Joseph: could you please try it again with a clean profile, as asked Paul on Comment 5?

Cheers,
Francesca

Comment 10

[Phoenix]

Resolved per whiteboard