Търсене в помощните статии

Избягвайте измамите при поддръжката. Никога няма да ви помолим да се обадите или изпратите SMS на телефонен номер или да споделите лична информация. Моля, докладвайте подозрителна активност на "Докладване за злоупотреба".

Научете повече

Latest firefox constantly stops responding for ~ 5 seconds and resumes.

  • 6 отговора
  • 1 има този проблем
  • 1 изглед
  • Последен отговор от Dimitris

more options

There isn't a specific usage pattern or a certain webpage that triggers this problem.

Tested with no addons loaded, got same result.
There isn't a specific usage pattern or a certain webpage that triggers this problem. Tested with no addons loaded, got same result.

Всички отговори (6)

more options

hi dimitris, would you be able to capture and share a performance profile while the problem is apparent?

https://developer.mozilla.org/en-US/docs/Mozilla/Performance/Reporting_a_Performance_Problem

more options

Hi Phillipp,

https://perfht.ml/2KgLDFD

Many thanks, Dimitris

more options

thanks, are you able to reproduce the hangs in firefox safemode as well? it looks like it may be a graphics issue, so updating your graphics drivers might help as well...

Troubleshoot extensions, themes and hardware acceleration issues to solve common Firefox problems

more options

It seems to be working fine in safe mode. Way speedier than normal, to be honest.

I'm on a Hyper-V VM, not possible to update video drivers I'm afraid... The issue is replicated on two different hyper-v servers (using the same OS image thought).

Since the last firefox update when the issue started occuring, there weren't any changes to the VM or the underlying hypervisors.

Thanks

more options

in this case i'd try to keep hardware acceleration disabled in Firefox's performance settings.

more options

Yeah, fair enough.

Disabling the acceleration seems to have helped.

Now the CPU usage goes a bit mental when rendering pages but looks like the annoying 5 sec freezing is no more.

I'll keep it disabled for the time being as it looks the workaround has helped, hoping a future release (or an MS patch) will fix it properly.

Thanks, Philipp Much appreciated.

Regards, Dimitris