InformAction Forums

Hi,

Not exactly sure of if it's noscript's fault but in firefox nightly when pasting a link from twitter into another tab it crashes then closes. However, if noscript is disabled it works fine. I tried the latest NS version and also 11.0.32 with the same result.

A link example
https://t.co/7ir9rF3iz3?amp=1

(Frikin frikin frikin, they removed about: !)


So you're saying, take your >https://t.co/7ir9rF3iz3?amp=1 link, open a tab in FF, Paste & Go, & the tab crashes?

Not seeing that here, 20200712214458.

Does it matter if you use the shortcut or the direct link to the page in question, https://www.hollywoodreporter.com/news/ ... er-1302969?

What permissions (sites) do you have allowed?
Do there need to be particular sites allowed to see this?
Is Allow Globally sufficient to see this?

NoScript, uBlock, FF 80


(So hollywood has this link, hottest bikinis, & I think, good.
And it opens some link to qsearch.io, which has some blocks, links like, bikini tops, & I think, good.
And it opens a yahoo search link, that returns - nothing!
Disappointed.
[Hah! Too funny. uBlock, enabled, blocks search.yahoo.com search results.
Regardless of fault, if yahoo can't deal with it, shake them.]
duckduckgo looks to require JavaScript. Shake them.)

Yeah it was some hollyweird trash site, it was the first link on the twitter page so I grabbed it.

They need to be actual twitter links from what I seeing, not regular ones. It's best to go to twitter and right click and copy a link into another tab.

It's also possible (will test tomorrow) that it's a bug with the the nightly, noscript and disabling e10s. To do that it's adding this environment variable:

MOZ_FORCE_DISABLE_E10S - 1

It appears related to javascript since it only does it when noscript is enabled. The NS permissions have twitter.com and twimg.com as trusted.

uBlock is installed but doesn't seem related either way. I've done a fresh install with NS only and had the same problem.

After some testing it seems to be related to noscript when e10s are disabled through the environment variable. I hope it gets taken a look at since so many of us are forced to disable multi-process as firefox runs so much better without it. If not, noscript will have to be disabled unless we can find what recent change Mozilla made to cause the bug.

Update: this is a bug related to noscript. I had to revert back down to v 11.0.29 for it to start working right again. It begins crashing in v 11.0.30 and is doing it in 78esr as well.

Any other minor details left out?
I'm still crash free (& never did quite follow the twitter end)?


(Disabling e10s does nothing to alleviate Sessions restore windows in random order. Sad.
But not to fear, we have Cortana - oh wait, that's Win10 - we have... Pocket .)

It's still doing it with 11.0.29, only half as much. Sometimes the links come in, other times the tab closes.

With a fresh profile and only NS installed the tab doesn't close, it just stays blank and never renders the page.

Guess I'll just stay on 68esr for now.

Guest wrote: ↑Tue Jul 14, 2020 2:35 am After some testing it seems to be related to noscript when e10s are disabled through the environment variable. I hope it gets taken a look at since so many of us are forced to disable multi-process as firefox runs so much better without it. If not, noscript will have to be disabled unless we can find what recent change Mozilla made to cause the bug.

That's unlikely to be fixed, and it can only get worse:
https://groups.google.com/g/mozilla.dev ... f-rx7TAwAJ

Thanks for the link, that explains what is causing the bug.

Reading that I'm more concerned they will eliminate the environment variable altogether. For now it looks like it's on hold so guess I'll have to live with it. Absolutely hate multi-process.

Guest wrote: ↑Wed Jul 15, 2020 10:55 pm Thanks for the link, that explains what is causing the bug.

I can't access that link, could someone please quote the relevant information here?

You need to sign into your google account, click the switch account link if you have one.

This is the revealing quote by Gijs Kruitbosch in the first post:

"Last week, we released Firefox 77, which turned out to break all
webpages sent using compression (like gzip) if you had disabled e10s
using this environment variable."

Kruitbosch then goes on to complain that unless the environment variable is done away with the world will come to an end. Fortunately there was pushback so for now it doesn't look like much is happening.

Finagle the URL a bit gets it working, https://groups.google.com/forum/#!msg/m ... f-rx7TAwAJ.

(First I had to see what a "normal" URL looked like, then it was just a matter of matching that - & hoping .)