Pesquisar no site de suporte

Evite golpes de suporte. Nunca pedimos que você ligue ou envie uma mensagem de texto para um número de telefone, ou compartilhe informações pessoais. Denuncie atividades suspeitas usando a opção “Denunciar abuso”.

Saiba mais

Esta discussão foi arquivada. Faça uma nova pergunta se precisa de ajuda.

YouTube 4K video playback performance issue on Windows 11

  • 5 respostas
  • 1 tem este problema
  • 1 exibição
  • Última resposta de 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'.

Solução escolhida

The issue has been resolved after updated to Firefox 100.

Thanks.

Ler esta resposta 👍 0

Todas as respostas (5)

more options

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

Alterado por mingsun123 em

more options

mingsun123 said

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

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.

more options

donthavecow said

You said Windows 11 but your screenshot is showing Mac?

That is the video....

more options

Solução escolhida

The issue has been resolved after updated to Firefox 100.

Thanks.