[FIXED; UNRELATED?] Firefox doesn't load with noscript
Posted: Thu Jan 20, 2022 3:27 am
Hello! I am having a strange problem with Firefox and noscript. I have some bad habits in my browsing: I keep 6 windows with hundreds of open tabs, and I don't reboot the PC for weeks until I am really forced to (by the ram use increasing until there is none left). So I didn't upgrade Firefox to the last version in the last few weeks. Noscript was upgraded by Firefox automatically to version 11.2.14 during this long period without a reboot.
Today I rebooted the PC (I am using Linux Mint) without upgrading Firefox, and when I tried to start Firefox again after the reboot, it didn't load any page. What happened was that Firefox gobbled a lot of RAM at the beginning, as usual (it gets usually to 5-6 GB after a few seconds), but instead of going down after that (usually, after all the open tabs in each windows is shown), it remained stuck a 5,6GB of RAM use. The cpu use instead was noticeably lower than what I am used to see at the start (I have the system monitor set to 100% for each core, so with a 4-cores cpu it can go to 400%. Usually when I start firefox it goes to 200-250% for a few seconds and then going down to almost zero, This time it west quickly to around 100%, then dropped to 50%... and stayed there.
The end result: all the six windows open, the tabs show the title of the page on the title bar, but they are empty, eternally loading, loading, but showing nothing. The CPU is stuck at 50%, RAM use is stuck at 5,5 GB, noscripts is shown on the page with the symbol it has usually on the system pages and clicking on it does nothing.
If I click on the "stop loading" X symbol on each of the six tabs, the CPU use goes down to zero, but the ram is still at 5,5GB, and nothing is shown, even if I try to reload the page.
If I open the Add-on page, it shows the "suggested add-on" but not noscript or any dictionary (it only shows the openh264 video codec, that was pre-installed)
And when I close Firefox, it goes down to around 1GB, and then firefox crashes...
I tried opening Firefox in safe mode, and it worked, everything worked fine. Noscript is the only Add-on I have installed, apart from the Italian Dictionary (I am italian, if you want we can use italian to talk, I am using english because this is an international forum). So I tried to upgrade it to the last version that I saw on the site, 11.2.15 (still being in safe mode), and tried to reboot the PC and firefox. But i got the same results. I tried to upgrade Firefox from 95.0.1 to 96.0.1 (and I applied every other upgrade suggested by mint for my version, I am still using Mint 19.3), but the results are the same.
Finally, after trying a lot of things, I found a temporary solution:
1) Start Firefox in safe mode, disable noscript, close firefox
2) Star Firefox normally, with noscript still disabled, so that Firefox start normally.
3) open the Add-on page and enable noscript. After that, everything works normally (I think, I am testing this right now but after one hour everything still works)
4) Remember to disable noscript before closing firefox, and in that case you can start at (2). If you forget, start again at (1)
After I found this solution this problem went from "help, I can't use my PC" level to the level of an annoyance, but it's really annoying. I am posting this hoping that you can solve this, and to help anybody else who has the same problem but didn't find that solution.
Today I rebooted the PC (I am using Linux Mint) without upgrading Firefox, and when I tried to start Firefox again after the reboot, it didn't load any page. What happened was that Firefox gobbled a lot of RAM at the beginning, as usual (it gets usually to 5-6 GB after a few seconds), but instead of going down after that (usually, after all the open tabs in each windows is shown), it remained stuck a 5,6GB of RAM use. The cpu use instead was noticeably lower than what I am used to see at the start (I have the system monitor set to 100% for each core, so with a 4-cores cpu it can go to 400%. Usually when I start firefox it goes to 200-250% for a few seconds and then going down to almost zero, This time it west quickly to around 100%, then dropped to 50%... and stayed there.
The end result: all the six windows open, the tabs show the title of the page on the title bar, but they are empty, eternally loading, loading, but showing nothing. The CPU is stuck at 50%, RAM use is stuck at 5,5 GB, noscripts is shown on the page with the symbol it has usually on the system pages and clicking on it does nothing.
If I click on the "stop loading" X symbol on each of the six tabs, the CPU use goes down to zero, but the ram is still at 5,5GB, and nothing is shown, even if I try to reload the page.
If I open the Add-on page, it shows the "suggested add-on" but not noscript or any dictionary (it only shows the openh264 video codec, that was pre-installed)
And when I close Firefox, it goes down to around 1GB, and then firefox crashes...
I tried opening Firefox in safe mode, and it worked, everything worked fine. Noscript is the only Add-on I have installed, apart from the Italian Dictionary (I am italian, if you want we can use italian to talk, I am using english because this is an international forum). So I tried to upgrade it to the last version that I saw on the site, 11.2.15 (still being in safe mode), and tried to reboot the PC and firefox. But i got the same results. I tried to upgrade Firefox from 95.0.1 to 96.0.1 (and I applied every other upgrade suggested by mint for my version, I am still using Mint 19.3), but the results are the same.
Finally, after trying a lot of things, I found a temporary solution:
1) Start Firefox in safe mode, disable noscript, close firefox
2) Star Firefox normally, with noscript still disabled, so that Firefox start normally.
3) open the Add-on page and enable noscript. After that, everything works normally (I think, I am testing this right now but after one hour everything still works)
4) Remember to disable noscript before closing firefox, and in that case you can start at (2). If you forget, start again at (1)
After I found this solution this problem went from "help, I can't use my PC" level to the level of an annoyance, but it's really annoying. I am posting this hoping that you can solve this, and to help anybody else who has the same problem but didn't find that solution.