Firefox freezes when loading most pages on The Guardian

[mark_b]

Below log is from https://www.tripadvisor.co.uk/Hotels-g1 ... otels.html (originally posted in another thread), XSS enabled and that Kaspersky exception in my ABE config. Still waay too slow. Strangely The Guardian seems absolutely fine for me.

I have Self-Destructing Cookies installed but I disabled it for this test load of that link. Is this any help?

Code: Select all

14:14:04.302 NoScript could not disable scripts for system global [System Principal] WinScript.js:13:11
14:14:04.409 “nsICookieManager2.getCookiesFromHost()” is changed. Update your code and pass the correct originAttributes. Read more on MDN: https://developer.mozilla.org/docs/Mozilla/Tech/XPCOM/Reference/Interface/nsICookieManager2  cookietracker.js:126:12
14:14:04.488 “nsICookieManager2.getCookiesFromHost()” is changed. Update your code and pass the correct originAttributes. Read more on MDN: https://developer.mozilla.org/docs/Mozilla/Tech/XPCOM/Reference/Interface/nsICookieManager2  cookietracker.js:82:12
14:14:48.734 TelemetryStopwatch: requesting elapsed time for nonexisting stopwatch. Histogram: "PLACES_AUTOCOMPLETE_6_FIRST_RESULTS_TIME_MS", key: "null"  TelemetryStopwatch.jsm:297
14:14:54.103 String.toLowerCase is deprecated; use String.prototype.toLowerCase instead  mootools-c-v23900594016a.js:1:43737
14:14:54.430 Use of getAttributeNode() is deprecated. Use getAttribute() instead.  mootools-c-v23900594016a.js:1:28075
14:14:54.430 Use of attributes' nodeValue attribute is deprecated. Use value instead.  mootools-c-v23900594016a.js:1:28097
14:15:03.090 about:blank : Unable to run script because scripts are blocked internally.  (unknown)

[mark_b]

OK so tripadvisor seems to be hit by the XSS performance issues, not the facebook part. I'm happy to try the next dev release to see if this fixes it. Thanks team!

[barbaz]

in the meanwhile as a work-around please try adding

Code: Select all

^https?://www.facebook.com/tr/

in the NoScript Options>Advanced>XSS exceptions box.

Unfortunately this doesn't seem to affect the hang on tripadvisor.

[Giorgio Maone]

Please check latest development build 5.0.6rc5, thanks.

[barbaz]

Please check latest development build 5.0.6rc5, thanks.

The tripadvisor link is MUCH better, thanks!


I'm still seeing a slight hang. But this one is not a NoScript bug. These steps clear it up -

1) NoScript Options > Advanced > ABE > USER, add

Code: Select all

Site .bluekai.com tpc.googlesyndication.com
Deny

2) NoScript Options > Advanced > XSS, add these exceptions

Code: Select all

^https?://tags\.bluekai\.com/
^https?://tpc\.googlesyndication\.com/

[mark_b]

Please check latest development build 5.0.6rc5, thanks.

I also see tripadvisor going much faster and usable again. Thanks Giorgio!!

[vmac]

Still the same problem with the new version 5.0.6
e.g. https://www.tripadvisor.de/Hotel_Review ... Kinki.html

[barbaz]

Still the same problem with the new version 5.0.6

Did you also follow the steps in viewtopic.php?p=88672#p88672 ?

[vmac]

No, because I thought NoScript will work like in former times - without any manipulations in the options.

But with the options above, it's still the same

[ginahoy]

I installed 5.0.6 last week and added the ABE rules and XSS exceptions suggested by barbaz several posts back. I also reverted from FF52 to FF51 for an unrelated reason. Overall, behavior has improved, but I'm now getting obtrusive warnings on eBay and several other sites. Here's a screenshot (typical): http://optimalbuilding.com/files/noscri ... enshot.jpg.

Admittedly I don't understand the intent of creating identical ABE rules and XSS exceptions, but I'd rather not have to put up with these warnings in order to avoid browser lockups. Perhaps if I understood what these changes are intended to do?

[barbaz]

@ginahoy known bug viewtopic.php?f=23&t=18996 . As workaround, replace Deny with

Code: Select all

Deny INC
Deny

[ginahoy]

Thanks, Barbaz, that did the trick!

[barbaz]

You're welcome!

[Thrawn]

Admittedly I don't understand the intent of creating identical ABE rules and XSS exceptions, but I'd rather not have to put up with these warnings in order to avoid browser lockups. Perhaps if I understood what these changes are intended to do?

The XSS filter exception tells NoScript not to do in-depth analysis and filtering of traffic to those sites - thus avoiding the freeze.

The ABE rule tells NoScript to simply block that traffic.

[ginahoy]

Ok, just so I understand... doesn't NS block scripts from domains that I forbid?