InformAction Forums

Temporarily Allow, Shortcut Key, Ctrl+Shift+\, Not Working in FF 56 - sometimes... ?

Why, where?
Good questions.

Well, I saw this once.
It did happen.
Haven't seen it again.
Maybe it was... on the initial install of extension, or maybe it was with a browser restart from Session Restore (or combination thereof)?

At least some windows, & all tabs in the particular window were affected.
But not all windows (& tabs therein) were.

Perhaps something like 5.1 Restartless Update breaks URL Bar and Tab Reload is related (but at the time I didn't notice anything particular in Error Console)?

Yesterday evening...

FF had been using, oh, 5-6 GB RAM or so, was using too much CPU [when IMO it should not have been], was generally running like crap.
So I Quit FF 56 for the evening.

FF reported it had "crashed", though AFAICT it shut down cleanly.

So now...
Upon starting from Session Restore (default method in my case)...


about:crashes shows:
https://crash-stats.mozilla.com/report/ ... 2710171006
https://crash-stats.mozilla.com/report/ ... fd10171006
https://crash-stats.mozilla.com/report/ ... 78a0171006
https://crash-stats.mozilla.com/report/ ... a490171006

Bug 1399847 Crash in IPCError-browser | ShutDownKill with FontCollectionBuilder
https://bugzilla.mozilla.org/show_bug.cgi?id=1399847



Anyhow, in some of my windows (29 it looks like) / tabs (unknown how many), Ctrl+\, shortcut key is not working.
(Pretty sure that if in a particular window the shortcut doesn't work, it doesn't work for any of the tabs in the window, even newly opened tabs in that window.)

Error Console is not pointing anything out (to me at least).

And now, having done very little in FF, its eating 25% CPU (100% of 1 core).

No clue.
Seems its made up of firefox.exe + a number of ucrtbase.dll threads that are doing the eating.

RAM is ~2 GB, but that's probably close to what is loaded from Session Restore.
(I'll have to check.)
Yes. ~1.8 GB on Safe Mode restart.


(But CPU is even higher, ~40%, & seems like it is not going subside.
Seems my not very extreme use case is blowing FF (55's) touting of "speedy startups" out of the water. Well maybe it is, perhaps, a bit faster loading, but...)

It has been a long times since I've rebooted...
(144 days.)

And yet another crash - which I didn't even know about until this morning.

https://crash-stats.mozilla.com/report/ ... eda1171006

Points (newly) to:

Bug 1405290 - Shutdownhang in mozilla::dom::workers::RuntimeService::Cleanup rising in Firefox 56
https://bugzilla.mozilla.org/show_bug.cgi?id=1405290

WONTFIX, for FF 56 + 57.
Maybe for FF 58.



Not going to open that particular Profile until... ? so will have to see what happens when I do.

Well, well, well.

SeaMonkey, this time. 2.49.1.
NoScript 5.1.2rc1.


SeaMonkey has NOT crashed in ages.
8 windows. ~700 MB RAM.

I start up this morning, from Session Restore, fine.
Go about what I need to do, fine.
Then, https://www.southwest.com/ ---> https://www.southwest.com/html/errors/j ... abled.html, "Oops! JavaScript Required.".

No problem, Ctrl+Shift+\.

NOT.

So it seems SeaMonkey + NoScript 5.1.2rc1 is affected also.
Again, not all windows affected...


?

therube wrote:?

Code: Select all

Key event not available on some keyboard layouts: key=“i” modifiers=“accel,alt,shift” id=“key_browserToolbox”  :: navigator.xul

That message is from SeaMonkey internals. Not related to NoScript or this issue.

Same problem

Ctrl+Shift+\ not working in Firefox 57, under Fedora or Ubuntu.

Ctrl+Shift+s brings up Firefox debug menu.

Thanks for the work guys will donate.

@blacktooth: This thread is about classic NoScript. NoScript 10 doesn't have shortcut keys implemented (yet?). You're looking for https://forums.informaction.com/viewtop ... 10&t=23595