Hi, after about half an hour I can't select any open tabs or see new tabs. When I reboot and restore previous session the new tabs appear.
Existing tabs can't be activated. I have no problem with restoring a previous session or opening previous tabs, but although new tabs are created - because I see them when I restart Firefox - they are invisible until I restart. Also, some, but not all of the menu options are not accessible until I restart.
Any advice would be appreciated,
Cheers,
Ian
Chosen solution
Hi philipp and cor-el, thanks for the advice regarding my problem with the tabs on Firefox freezing. After starting in Safe Mode, I think I've identified that the problem was an add-on, which had enabled me to manage and save Firefox sessions.
Read this answer in context 👍 0All Replies (6)
hello ian, can you try to replicate this behaviour when you launch firefox in safe mode once? if not, maybe an addon is interfering here...
Troubleshoot extensions, themes and hardware acceleration issues to solve common Firefox problems
Boot the computer in Windows Safe Mode with network support (press F8 on the boot screen) as a test to check if other software is causing this.
Chosen Solution
Hi philipp and cor-el, thanks for the advice regarding my problem with the tabs on Firefox freezing. After starting in Safe Mode, I think I've identified that the problem was an add-on, which had enabled me to manage and save Firefox sessions.
Hi again philipp and cor-el, unfortunately I still have the same problem with the tabs on Firefox freezing, even after removing the 'Manage Browse Sessions' add-on. I'm wondering now if the issue may be that I rarely power off my computer - I always hibernate it or sleep it, unless I need to install updates. Does that seem likely? Many thanks in anticipation of any advice, Beeyin
Did you try to disable hardware acceleration in Firefox?
- Tools > Options > Advanced > General > Browsing: "Use hardware acceleration when available"
You need to close and restart Firefox after toggling this setting.
Thanks cor-el, fingers crossed, disabling hardware acceleration does seem to have solved the problem this time. Beeyin