Memory leak + high cpu usage, 64-bit linux
-
Oleg
Memory leak + high cpu usage, 64-bit linux
Hi! I have a problem with NoScript (2.6.9.25), Firefox 38.0.1 64-bit Linux (openSUSE, from repos or Mozilla's tarball - same behaviour).
On some sites (for example http://rutracker.org/) with NoScript enabled Firefox eats 100% of 1 CPU core and quickly grows up to 10Gb RAM. After that it starts freezing and eventually crashes. When it happens the progress indicator (in tab) for problematic site spins forever. Doesn't matter if scripts allowed or blocked on this particular site. Same thing with new profile.
On some sites (for example http://rutracker.org/) with NoScript enabled Firefox eats 100% of 1 CPU core and quickly grows up to 10Gb RAM. After that it starts freezing and eventually crashes. When it happens the progress indicator (in tab) for problematic site spins forever. Doesn't matter if scripts allowed or blocked on this particular site. Same thing with new profile.
Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Firefox/38.0
Re: Memory leak + high cpu usage, 64-bit linux
Assuming that disabling NoScript entirely gets rid of that behavior...
When that happens, do you see anything related in the Browser Console? (Ctrl-Shift-J)
(if you don't know what's related, turn off CSS warnings and post everything else you see)
You may need to open the browser console before you open the site...
When that happens, do you see anything related in the Browser Console? (Ctrl-Shift-J)
(if you don't know what's related, turn off CSS warnings and post everything else you see)
You may need to open the browser console before you open the site...
*Always* check the changelogs BEFORE updating that important software!
-
-
Oleg
Re: Memory leak + high cpu usage, 64-bit linux
Thanks for the quick answer
With NoScript enabled:
With NoScript enabled:
With NoScript disabled:JavaScript 1.6's for-each-in loops are deprecated; consider using ES6 for-of instead ScriptSurrogate.js:346:1634
The resource at "http://top100-images.rambler.ru/top100/ ... -gray2.gif" was blocked because tracking protection is enabled. index.php
The resource at "http://counter.rambler.ru/top100.scn?14 ... 883794&rf=" was blocked because tracking protection is enabled. index.php
btw, tracking protection has no effect on this behaviourThe resource at "http://top100-images.rambler.ru/top100/ ... -gray2.gif" was blocked because tracking protection is enabled. index.php
The resource at "http://counter.yadro.ru/hit?t16.2;r;s19 ... 6263072795" was blocked because tracking protection is enabled. index.php
The resource at "http://counter.rambler.ru/top100.scn?14 ... 648188&rf=" was blocked because tracking protection is enabled. index.php
This site makes use of a SHA-1 Certificate; it's recommended you use certificates with signature algorithms that use hash functions stronger than SHA-1.[Learn More] 12991294
This site makes use of a SHA-1 Certificate; it's recommended you use certificates with signature algorithms that use hash functions stronger than SHA-1.[Learn More] 28584306
This site makes use of a SHA-1 Certificate; it's recommended you use certificates with signature algorithms that use hash functions stronger than SHA-1.[Learn More]
Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Firefox/38.0
Re: Memory leak + high cpu usage, 64-bit linux
What is the latest rc version of NoScript which does not have this problem?
old noscript @
https://addons.mozilla.org/addon/noscript/versions
*or*
https://noscript.net/feed?t=a
If you can't determine that, can you disable a few individual NoScript features one at a time to try determine which one is causing the slow down, re-enabling each after the test?
1) XSS: NoScript Options > Advanced > XSS, un-check everything
2) ABE: NoScript Options > Advanced > ABE > un-check "Enable ABE"
-> 2a) if that works, try re-enabling ABE and setting about:config > noscript.doNotTrack.enabled to false
3) ClearClick: NoScript Options > Advanced > ClearClick, un-check everything
4) Inclusion type checking: about:config > set noscript.inclusionTypeChecking to false
5) The other XSS filter: about:config > set noscript.xss.checkInclusions to false
6) surrogates: about:config > noscript.surrogate.enabled to false
7) well, whatever I didn't mention that's listed in viewtopic.php?f=10&t=5920
old noscript @
https://addons.mozilla.org/addon/noscript/versions
*or*
https://noscript.net/feed?t=a
If you can't determine that, can you disable a few individual NoScript features one at a time to try determine which one is causing the slow down, re-enabling each after the test?
1) XSS: NoScript Options > Advanced > XSS, un-check everything
2) ABE: NoScript Options > Advanced > ABE > un-check "Enable ABE"
-> 2a) if that works, try re-enabling ABE and setting about:config > noscript.doNotTrack.enabled to false
3) ClearClick: NoScript Options > Advanced > ClearClick, un-check everything
4) Inclusion type checking: about:config > set noscript.inclusionTypeChecking to false
5) The other XSS filter: about:config > set noscript.xss.checkInclusions to false
6) surrogates: about:config > noscript.surrogate.enabled to false
7) well, whatever I didn't mention that's listed in viewtopic.php?f=10&t=5920
*Always* check the changelogs BEFORE updating that important software!
-
-
Oleg
Re: Memory leak + high cpu usage, 64-bit linux
The oldest one I tried is 2.6.8.43. Same problem.
But disabling ABE helps. When I disable ABE the spinning progress indicator (which spins forever on problematic site) immediately stops, CPU and RAM usage drops down. Setting noscript.doNotTrack.enabled to false doesn't change anything.
But disabling ABE helps. When I disable ABE the spinning progress indicator (which spins forever on problematic site) immediately stops, CPU and RAM usage drops down. Setting noscript.doNotTrack.enabled to false doesn't change anything.
Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Firefox/38.0
Re: Memory leak + high cpu usage, 64-bit linux
Do you have any non-default ABE rules?
If so can you please post them and might they be active on the "problematic" sites?
If so can you please post them and might they be active on the "problematic" sites?
*Always* check the changelogs BEFORE updating that important software!
-
-
Oleg
Re: Memory leak + high cpu usage, 64-bit linux
Nope. I don't have any custom ABE rules.
SYSTEM
SYSTEM
USER# Prevent Internet sites from requesting LAN resources.
Site LOCAL
Accept from LOCAL
Deny
Checkbox "Allow sites to push their own rulesets" unchecked# User-defined rules. Feel free to experiment here.
Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Firefox/38.0
Re: Memory leak + high cpu usage, 64-bit linux
about:crashes, last few related URLs?eventually crashes
Odd.Doesn't matter if scripts allowed or blocked on this particular site. Same thing with new profile.
What Plugins do you have?
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14 Pinball NoScript FlashGot AdblockPlus
Mozilla/5.0 (Windows NT 5.1; rv:36.0) Gecko/20100101 SeaMonkey/2.33.1
-
Oleg
Re: Memory leak + high cpu usage, 64-bit linux
https://crash-stats.mozilla.com/report/ ... 49e2150525therube wrote:about:crashes, last few related URLs?eventually crashes
Odd.Doesn't matter if scripts allowed or blocked on this particular site. Same thing with new profile.
What Plugins do you have?
Plugins: Java 1.7 (Oracle), OpenH264 by Cisco, Shockwave Flash (disabled). Same thing without any plugins (removed from plugins dir, not just disabled)
Extensions in addition to NS: xclear, adblock, opensuse firefox extensions Again, no matter if they are enabled or disabled.
Last edited by barbaz on Wed May 27, 2015 3:29 am, edited 1 time in total.
Reason: fix link
Reason: fix link
Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Firefox/38.0
-
Oleg
Re: Memory leak + high cpu usage, 64-bit linux
Proper crash url https://goo.gl/YQjovB
Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Firefox/38.0
Re: Memory leak + high cpu usage, 64-bit linux
I don't like clicking on shortened links so I've fixed it in your above post as follows:Oleg wrote:Proper crash url
Code: Select all
[url=LINK_HERE]text you see of the link[/url]Also if that bug report linked by your crash report is any indicator, that crash is indeed a NoScript bug.
*Always* check the changelogs BEFORE updating that important software!
-
-
Oleg
Re: Memory leak + high cpu usage, 64-bit linux
So where should I report this bug?
Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Firefox/38.0
Re: Memory leak + high cpu usage, 64-bit linux
Unless you want to register an account on this board, this is probably the right place to report it...Oleg wrote:So where should I report this bug?
If you register an account we'll move this to NoScript Development; otherwise, it can stay here, it's fine.
*Always* check the changelogs BEFORE updating that important software!
-
-
hippo-upy
Re: Memory leak + high cpu usage, 64-bit linux
I can confirm a similar problem on Mac OS X 8.5 / Firefox 38.0.1 .
After receiving the V. 2.6.9.24 noscript update, browser tabs were flickering on site-load, and browser-window repaints were having a grand mal seizure.
I disabled noscript and had no problems.
I tried V. 2.6.9.25 and had the same problems, so I completely uninstalled and trashed all items and folders: Mozilla, Firefox, Google, etc. from both root and user directories; re-installed Firefox and noscript and same problem exists. Disabled noscript again and had no problems.
After receiving the V. 2.6.9.24 noscript update, browser tabs were flickering on site-load, and browser-window repaints were having a grand mal seizure.
I disabled noscript and had no problems.
I tried V. 2.6.9.25 and had the same problems, so I completely uninstalled and trashed all items and folders: Mozilla, Firefox, Google, etc. from both root and user directories; re-installed Firefox and noscript and same problem exists. Disabled noscript again and had no problems.
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:38.0) Gecko/20100101 Firefox/38.0
Re: Memory leak + high cpu usage, 64-bit linux
@hippo-upy: did you mean to post that in viewtopic.php?f=7&t=20847 ?
*Always* check the changelogs BEFORE updating that important software!
-