Join the Mozilla’s Test Days event from Dec 2–8 to test the new Firefox address bar on Firefox Beta 134 and get a chance to win Mozilla swag vouchers! 🎁

搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

Opening Links in New Tabs is Slow and Laggy

  • 2 个回答
  • 11 人有此问题
  • 1 次查看
  • 最后回复者为 kaiyangl

more options

Since updating to Firefox 57 (Quantum), opening links in new tabs are slow and laggy. Opening a new tab is not an issue, the specific act of opening a link in new tab is the one that causes the issue. Firefox would freeze for 3-5 seconds before responding and opening the new tab. This has happened twice. The first time was the first few hours after I updated to Firefox 57 before it magically fixed itself. Now 1 and a half month later the problem has resurfaced again for the second time. I'm not exactly sure whats wrong with it. I've tried refreshing Firefox, as well as the other solutions on the forum, but to no avail. Any help is much appreciated.

Since updating to Firefox 57 (Quantum), opening links in new tabs are slow and laggy. Opening a new tab is not an issue, the specific act of opening a link in new tab is the one that causes the issue. Firefox would freeze for 3-5 seconds before responding and opening the new tab. This has happened twice. The first time was the first few hours after I updated to Firefox 57 before it magically fixed itself. Now 1 and a half month later the problem has resurfaced again for the second time. I'm not exactly sure whats wrong with it. I've tried refreshing Firefox, as well as the other solutions on the forum, but to no avail. Any help is much appreciated.

被采纳的解决方案

please : go to the Firefox 3 Bar Menu --> Options --> Privacy & Security panel and under Permissions check (put a tick in the box) the setting to Prevent Accessibility Services from accessing your browser.

Monitor in Task Manager. Should stay below 2 gigs. If excessive then do below and monitor and change if need to...Test and go up again , go back down, it will eventually get a zone you and it can live with.

Go to the 3 Bar Menu then Options --> General --> Performance and untick everything. change the recommended size lower then see how it runs. Note: 1 = No Multiprocessor = slow again. Try 2 Restart Firefox after making these changes please.

Please let us know if this solved your issue or if need further assistance.

定位到答案原位置 👍 7

所有回复 (2)

more options

选择的解决方案

please : go to the Firefox 3 Bar Menu --> Options --> Privacy & Security panel and under Permissions check (put a tick in the box) the setting to Prevent Accessibility Services from accessing your browser.

Monitor in Task Manager. Should stay below 2 gigs. If excessive then do below and monitor and change if need to...Test and go up again , go back down, it will eventually get a zone you and it can live with.

Go to the 3 Bar Menu then Options --> General --> Performance and untick everything. change the recommended size lower then see how it runs. Note: 1 = No Multiprocessor = slow again. Try 2 Restart Firefox after making these changes please.

Please let us know if this solved your issue or if need further assistance.

more options

Pkshadow said

please : go to the Firefox 3 Bar Menu --> Options --> Privacy & Security panel and under Permissions check (put a tick in the box) the setting to Prevent Accessibility Services from accessing your browser. Monitor in Task Manager. Should stay below 2 gigs. If excessive then do below and monitor and change if need to...Test and go up again , go back down, it will eventually get a zone you and it can live with. Go to the 3 Bar Menu then Options --> General --> Performance and untick everything. change the recommended size lower then see how it runs. Note: 1 = No Multiprocessor = slow again. Try 2 Restart Firefox after making these changes please. Please let us know if this solved your issue or if need further assistance.

Thank you! Changing it to 2 content process limit solved my problem. I also eventually found that my antivirus was hogging up the processing power for some reason and restarting it solved this problem as well.