Avatar for Username

Mozilla サポートの検索

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.

詳しく学ぶ

このスレッドはアーカイブに保管されました。 必要であれば新たに質問してください。

YouTube 4K video playback performance issue on Windows 11

  • 5 件の返信
  • 1 人がこの問題に困っています
  • 1 回表示
  • 最後の返信者: mingsun123

mingsun123
mingsun123
more options

I had been using Firefox browser for awhile, but because of playback performance issue, I have to using another browser just for video playing, especially for 4K video.

Compared to Edge, Firefox seems taking more resources to playback the YouTube video and more heat. When look at the Task Manager, the Video Processing is 0%, and GPU is running significantly more resources on '3D'.

I had been using Firefox browser for awhile, but because of playback performance issue, I have to using another browser just for video playing, especially for 4K video. Compared to Edge, Firefox seems taking more resources to playback the YouTube video and more heat. When look at the Task Manager, the Video Processing is 0%, and GPU is running significantly more resources on '3D'.

選ばれた解決策

The issue has been resolved after updated to Firefox 100.

Thanks.

この回答をすべて読む 👍 0

すべての返信 (5)

mingsun123
mingsun123 質問者
more options

This is the screenshots I got, the image from the left is from Firefox & next is from Edge. The YouTube Links: here

この投稿は mingsun123 により に変更されました

-elison-
-elison-
more options

mingsun123 said

Hello! Does it still happen in Troubleshoot Mode?: Diagnose Firefox issues using Troubleshoot Mode

mingsun123
mingsun123 質問者
more options

-elison- said

mingsun123 said

Hello! Does it still happen in Troubleshoot Mode?: Diagnose Firefox issues using Troubleshoot Mode

It even worst, and video playback was lagging.

mingsun123
mingsun123 質問者
more options

donthavecow said
You said Windows 11 but your screenshot is showing Mac?

That is the video....

mingsun123
mingsun123 質問者
more options

選ばれた解決策

The issue has been resolved after updated to Firefox 100.

Thanks.