NoScript causing a bug on FireFox 57

[Guest]

Every time I open up "Preferences" and check the "Allow all scripts globally" (While the add-on is enabled), after that whatever open tab (which has a website open already) I visit, turns black completely. The whole entire tab becomes black and affects all other tabs as well. I have to disable NoScript and restart browser to get rid of the issue.

How do I fix this?

[hcbd]

For me (on Fedora 27) firefox 57 gets verrrryy buggy when opening the no-script settingspage. clicking the icon --> click 'noscript' logo top right to open this page.
Opening this page will blackout/blockout/disrupt rendering on other webpages/tabs (even about:home) and will sometimes completely lock up firefox.
Also selecting the Debug function on the bottom of the settingspage will make the page duplicate itself beneath the textbox that will appear.
Is this a bug in firefox or in the settingspage of NoScript?

[Guest]

For me (on Fedora 27) firefox 57 gets verrrryy buggy when opening the no-script settingspage. clicking the icon --> click 'noscript' logo top right to open this page.
Opening this page will blackout/blockout/disrupt rendering on other webpages/tabs (even about:home) and will sometimes completely lock up firefox.
Also selecting the Debug function on the bottom of the settingspage will make the page duplicate itself beneath the textbox that will appear.
Is this a bug in firefox or in the settingspage of NoScript?

OP of thread here. I have the same exact issue!

I believe its a bug with NoScript because I noticed that somehow only tabs that I visit after opening the NoScript settingpage get affected by the bug.

This is how I came to the conclusion:

7 Tabs open. All have websites opened.

1. Go to settings page of NoScript.
2. Switch to 3 different tabs.
3. All those 3 tabs become black.
4. Disable NoScript
5. Open the 3 black tabs.
6. Black tabs are still black
7. Open the remaining tabs
8. Remaining tabs are not blacked out.

[Giorgio Maone]

Does it happen on a clean profile with just NoScript enabled?

[Guest]

Does it happen on a clean profile with just NoScript enabled?

I setup a clean profile with NoScript enabled and the bug was unable to be produced.

So it passes a clean profile BUT then I tried to install more add-ons on the "clean" profile. Any add-on that I installed (with the NoScript already enabled), the bug was re-produced.

These are the add-ons that I have on my main profile and tested on the clean profile:

Adblock Plus
Ghostery
HTTPS-Everywhere

Here are my reproduction Steps:

1. Have NoScript Enabled
2. Open any website
3. Go into NS settings
4. Click the "clock" on any link from the settings page. Preferably if the link affects the "opened" website. Ex: If you have Netflix opened then click the clock of Netflix from the add-on management settings menu.
5. Wait 2-3 seconds
6. Click on any new tab or the tab which has website already opened.
7. Blackout or tab crashed warning from Firefox

[alex.forencich]

Seeing the same here. Unclear if this is a noscript bug or a firefox bug. Either way, it's a critical stability issue. When this is triggered, firefox prints messages like

Code: Select all

[GFX1-]: Failed 2 buffer db=0 dw=0 for 0, 0, 24, 24
[Parent 4186, Main Thread] WARNING: file /build/firefox/src/mozilla-unified/ipc/chromium/src/base/shared_memory_posix.cc, line 216

[Guest]

Seeing the same here. Unclear if this is a noscript bug or a firefox bug. Either way, it's a critical stability issue. When this is triggered, firefox prints messages like

Code: Select all

[GFX1-]: Failed 2 buffer db=0 dw=0 for 0, 0, 24, 24
[Parent 4186, Main Thread] WARNING: file /build/firefox/src/mozilla-unified/ipc/chromium/src/base/shared_memory_posix.cc, line 216

Seems like it is affecting FF 56 and 57. Does you have any other add-ons enabled with NS?

[Guest]

Apart from the 3 people already on this thread, this very same issue seems to be affecting many others:

1. https://hackademix.net/2017/11/21/top-i ... ment-38717
2. https://hackademix.net/2017/11/21/top-i ... ment-38630
3. https://hackademix.net/2017/11/21/top-i ... ment-38581

In total there are 6 documented cases. I'm sure it is affecting other people who have not yet reported it therefore it can be classified as a bug at this point due to the numbers. We can not continue to assume that this is just a glitch.

Does any one have any solution?

[Guest]

I am having the same issue. I am on a Linux workstation with FF 57. When opening up NoScript's settings page, the entire browser locks up for about 60 seconds and I can't get out of the tab. If I minimize FF with the window manager, upon restoring the window it comes back as a grayed out window until the lock clears up.

[Guest]

Anyone have any idea when this bug would be fixed?