Page 1 of 1
Firefox shutdown time increased
Posted: Sun Oct 29, 2017 2:08 pm
by nspls
If I open many tabs and close FF, the process will stay on Taskmanager for many seconds, also increasing its memory even x2 before shutting down.
With Noscript disabled this doesn't happen.
Now I'm on v5.1.4, but I had this problem on v5.1.3 too.
P.S.: while this is investigated, can I downgrade to v5.1.2 without losing my settings?
Re: Firefox shutdown time increased
Posted: Sun Oct 29, 2017 2:28 pm
by Giorgio Maone
nspls wrote:
P.S.: while this is investigated, can I downgrade to v5.1.2 without losing my settings?
Yes you can, and please confirm whether this actually does not happen there.
Most likely, though, this might be due to the extra cleanup work that NoScript must perform now that it is restartless and cannot leave any mess behind.
Re: Firefox shutdown time increased
Posted: Sun Oct 29, 2017 4:17 pm
by barbaz
Re: Firefox shutdown time increased
Posted: Sun Oct 29, 2017 4:31 pm
by therube
Not seeing anything on my end.
1. open from session restore, then close
2. open from session restore, enable hardware acceleration, then close
3. open from session restore, hardware acceleration enabled, then close
Win7 x64
FF 56 x64
Oh, nevermind - NoScript 5.0.10rc4, oops.
Anyhow...
44 windows, 960 tabs
e10s disabled (cause of Legacy extensions, incl. NoScript)
Note that FF is using ~10% CPU, never ending - doing nothing.
Re: Firefox shutdown time increased
Posted: Sun Oct 29, 2017 5:08 pm
by therube
With NoScript 5.1.4.
Again not seeing a spike (or variance) in memory usage on FF close.
FF 56
does exit memory quickly. (FF 56 made changes in that respect compared to earlier.)
I have seen, on browser close, in the past, memory usage vary - dropping then going back up, before going back down again & finally exiting memory completely.
Didn't time startup.
Subjectively (so meaningless) 56 & NoScript 5.0.10 did seem to load quicker then with 5.1.14.
Closing is not an issue at all. (It is very fast at that.)
1. open from session restore, then close, NoScript 5.0.10
2. open from session restore, enable hardware acceleration, then close
3. open from session restore, with hardware acceleration enabled, then close
4. open from session restore, with hardware acceleration enabled, NoScript 5.1.4, then close
https://s25.postimg.org/pi1z7h8m5/Firef ... _no_sp.png
Re: Firefox shutdown time increased
Posted: Sun Oct 29, 2017 6:32 pm
by nspls
Ok, I put v5.1.2 (it took a while), closed FF and it closed in a couple of seconds. I started FF, closed, and it did it in ~60 seconds (ram almost doubling).
I then opened FF and disabled NS: FF froze for like 40 seconds while the ram increased while it was disabling; I then restarted FF a couple of time without any problem.
What now?
On a side note: with v5.1.2 bookmarklets do open, while with v5.1.4 nothing happens, unless the site is whitelisted, is this intended?.
Re: Firefox shutdown time increased
Posted: Sun Oct 29, 2017 6:37 pm
by barbaz
nspls wrote:On a side note: with v5.1.2 bookmarklets do open, while with v5.1.4 nothing happens, unless the site is whitelisted, is this intended?.
No.
https://forums.informaction.com/viewtop ... 10&t=23468
Re: Firefox shutdown time increased
Posted: Sun Oct 29, 2017 7:38 pm
by Giorgio Maone
Do you have e10s disabled?
Re: Firefox shutdown time increased
Posted: Mon Oct 30, 2017 2:03 pm
by nspls
Giorgio Maone wrote:
Do you have e10s disabled?
Yes.
Re: Firefox shutdown time increased
Posted: Tue Nov 07, 2017 2:09 pm
by nspls
Sorry, how far can I downgrade Noscript without losing my settings? I want to test older versions.