Description
We got a case where a host encountered issues when sharing his screen.
This is due to low CPU specs on his machine and we already know that the zoom web SDK would for example automatically deactivate his video if low CPU conditions are detected.
But here we had the opposite effect: his video continued to stream to the other participant, but the other participant video was deactivated time to time until he stopped to share his screen.
Details
The screen share started at 16:07 and finished around 16:33.
We can see a drop of the frame rate as soon as the screen sharing starts, showing a potential CPU lack. Audio was also affected at same time, introducing packet loss as well on the audio received.
Here is the video graph of the host:
The host did not deactivate / reactivate the other participant video, and the other participant video is still streamed all along, here is the other participant view:
As shortly explained, we know that zoom web SDK would stop the video of the participant sharing the screen if CPU is lacking. But this did not happen here, and instead we can see a deactivation of the received video time to time.
Could you please investigate on that & explain to us how this can happen ? I can provide you the meeting ID if you need it.
Which version?
1.8.1
To Reproduce(If applicable)
Not reproducible
Device (please complete the following information):
- Device: Chrome OS
- Browser: Latest chrome release for chrome OS
Additional context
Add any other context about the problem here.