This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Diminishing performance (increasing lag) the longer Firefox 133 is open

more options

I believe this problem began in 133. I've noticed that if FF is open for a few hours, it starts to develop a very noticeable input lag. For example, if I'm watching a YouTube video and hit an arrow key to advance the video, there will be a couple of seconds before the browser registers the key press. It behaves like a high CPU issue but I do not detect high CPU usage when this is happening. Restarting the browser resolves the issue for a few hours.

This is happening on Windows 11 as well as on a Mac running Sonoma.

I believe this problem began in 133. I've noticed that if FF is open for a few hours, it starts to develop a very noticeable input lag. For example, if I'm watching a YouTube video and hit an arrow key to advance the video, there will be a couple of seconds before the browser registers the key press. It behaves like a high CPU issue but I do not detect high CPU usage when this is happening. Restarting the browser resolves the issue for a few hours. This is happening on Windows 11 as well as on a Mac running Sonoma.

All Replies (3)

more options

Helpful?

more options

I haven't tried that yet. It usually takes a few hours before the problem appears and it's intermittent. It might take a while to see if it appears in Troubleshoot Mode.

Helpful?

more options

Also, I'm not sure this is related, but after some time I also notice that it starts to become difficult to click on URL links. As with the other issue, restarting the browser clears it up. I believe both of these issues began in v133.

Helpful?

Ask a question

You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.