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 closed and archived. Please ask a new question if you need help.

Screensharing and Cam sharing seems to spike the CPU utlisation by firefox

  • 1 reply
  • 1 has this problem
  • 14 views
  • Last reply by McCoy

more options

Hi,

     After couple of recent updates in firefox I am having issues with Webrtc content. The Screenshare and the camshare in done on firefox I could see that the firefox CPU utlisation is spiking to 30-40% and I have also observed that a process named Desktop Window Manager in also cosuming the CPU drastically its in Windows OS and ,similarly it is FireFoxCP Web Content  in Mac machines. If the screensharing and cam sharing is left running for a while the CPU utlisation is to touch 100% and the system will slowdown and sometimes firefox crashes. I have tried running the same application in chrome browser and the CPU utlisation is 5-10%. I have attached a screenshot of my test.

I have tried clearing the cookies history etc and running the Firefox in its safe mode the issue still exist. Does anyone knows how to fix this issue and Is anyone having the same issue?

Hi, After couple of recent updates in firefox I am having issues with Webrtc content. The Screenshare and the camshare in done on firefox I could see that the firefox CPU utlisation is spiking to 30-40% and I have also observed that a process named Desktop Window Manager in also cosuming the CPU drastically its in Windows OS and ,similarly it is FireFoxCP Web Content in Mac machines. If the screensharing and cam sharing is left running for a while the CPU utlisation is to touch 100% and the system will slowdown and sometimes firefox crashes. I have tried running the same application in chrome browser and the CPU utlisation is 5-10%. I have attached a screenshot of my test. I have tried clearing the cookies history etc and running the Firefox in its safe mode the issue still exist. Does anyone knows how to fix this issue and Is anyone having the same issue?

All Replies (1)

more options

Duplicate to :

https://support.mozilla.org/en-US/questions/1255393

(where there is a screenshot attachted)