We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Avatar for Username

搜索 | 用户支持

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

详细了解

话题已存档。 如果需要帮助请提出新问题。

Firefox unresponsive across USB to VGA or USB to DVI adapters?

  • 2 个回答
  • 14 人有此问题
  • 3 次查看
  • 最后回复者为 vmikayel

536548
536548
more options

Firefox (and Thunderbird) are both completely unusable when you move their windows to the external display using either USB to VGA or USB to DVI adapters. The problem occurs using two different USB to VGA/DVI brands, and Mozilla software is the only software the problem occurs with. It's not always crashing, but instead like it can't render itself. You can't resize, maximize, or minimize the windows without them becoming responsive. All other applications work fine. Is there a bug? Are there rendering settings in about:config I can adjust? This is a major issue and I'll probably be forced to use IE or Chrome on these machines if this isn't fixable. I found one other post regarding this from Firefox version 4.0.2, but no solutions or responses to that. Any suggestions or solutions?

Firefox (and Thunderbird) are both completely unusable when you move their windows to the external display using either USB to VGA or USB to DVI adapters. The problem occurs using two different USB to VGA/DVI brands, and Mozilla software is the only software the problem occurs with. It's not always crashing, but instead like it can't render itself. You can't resize, maximize, or minimize the windows without them becoming responsive. All other applications work fine. Is there a bug? Are there rendering settings in about:config I can adjust? This is a major issue and I'll probably be forced to use IE or Chrome on these machines if this isn't fixable. I found one other post regarding this from Firefox version 4.0.2, but no solutions or responses to that. Any suggestions or solutions?

所有回复 (2)

EnricoBassetti
EnricoBassetti
more options

A possibile workaround is setting layers.acceleration.disabled to true.

vmikayel
vmikayel
more options

Workaround with layers.acceleration.disabled did not do it for me. What fixed it is simply disabling acceleration via menu "Tools->Options->Advanced->General->Use Hardware Acceleration when available". FF version is 12.0