Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

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.

Avatar for Username

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

This thread was archived. Please ask a new question if you need help.

Opening a new tab while a second monitor is connected but disabled freezes firefox for a second.

  • 2 replies
  • 1 has this problem
  • 1 view
  • Last reply by Tntmister

Tntmister
Tntmister
more options

Whenever i open a new tab in Firefox while having a second monitor connected but disabled, Firefox freezes for a second.

If i unplug the monitor the problem stops and if i enable the monitor the problem also stops.

Running Firefox in safe mode didn't fix the issue.

I'm on a laptop if it is any help.

Whenever i open a new tab in Firefox while having a second monitor connected but disabled, Firefox freezes for a second. If i unplug the monitor the problem stops and if i enable the monitor the problem also stops. Running Firefox in safe mode didn't fix the issue. I'm on a laptop if it is any help.

All Replies (2)

Eve
Eve
more options

Does this behavior occur in FF73 (https://www.mozilla.org/en-US/firefox/developer/) and FF74 (https://www.mozilla.org/en-US/firefox/74.0a1/releasenotes/)

Maybe it's a bug that's been corrected in future versions.

Tntmister
Tntmister Question owner
more options

evhenry said

Does this behavior occur in FF73 (https://www.mozilla.org/en-US/firefox/developer/) and FF74 (https://www.mozilla.org/en-US/firefox/74.0a1/releasenotes/) Maybe it's a bug that's been corrected in future versions.

In the developer version and the nightly and the behavior persists in both.