1359377 - Delayed visual notification for the initiator of share screen using appear.in service

Status: RESOLVED INVALID

(Core :: WebRTC: Audio/Video, defect, P2)

Description

[Bogdan Maris [:bogdan_maris], Release Desktop QA]

[Affected versions]:
- Firefox 53.0
- Firefox 54 beta 1
- latest Nightly 55.0a1

[Affected platforms]:
- Mac OS X 10.11
- Ubuntu 16.04 32bit
- Windows 10 64bit

[Steps to reproduce]:
1. Start Firefox
2. Visit https://appear.in/ and create a room
3. Click on Share Screen

- It would help to have another person joining the room because when user 1 clicks Share Screen, user 2 will get visual notification immediately and user 1 will get a delayed visual notification (the delay can take seconds, up to 1 minute)

[Expected result]:
- User that initiates the Share screen receives notification that the screen was shared (A screen showing what it's shared and Share Screen button changes to Stop Sharing).

[Actual result]:
- User that initiates the Share Screen receives delayed notifications that the screen was shared (A screen showing what it's shared and Share Screen button changes to Stop Sharing).

[Regression range]:
- This is not a recent regression, I was able to reproduce this back to Fx 47.

[Additional notes]:
- This issue does not reproduce if a user from Chrome initiates Share screen, maybe because on Chrome an extension is required to be installed in order to Share screen.

Comment 1

[Michael Froman [:mjf]]

I am also able to reproduce this behavior.

Comment 2

[Randell Jesup [:jesup] (needinfo me)]

I can reproduce, but this appears to be a site problem.

The sharing indicator at the top of the screen changes immediately (as it should).  The display in the page sometimes takes a fair bit of time to change -- but that's totally under the control of the application.

Fippo?

Comment 3

[Philipp Hancke [:fippo]]

this seems to be mostly an application problem. As far as I can see this is showing up at the same time the resize event listener is called when you paste this into the console:
  var v = document.querySelector('video');
  v.addEventListener('resize', () => {console.log('RESIZE', v.videoWidth); });

I thought this could be related to replaceTrack but it also happens without any peers or peerconnections. This looks like a regression on our end where we do weird stuff with cloned streams, will take a look!

Comment 4

[Randell Jesup [:jesup] (needinfo me)]

Thanks fippo..  If there is anything at our end, let us know and file a new bug.

Comment 5

[Philipp Hancke [:fippo]]

Turned out to be the angular digest loop being _very_ slow. So what pehrsons complains about all the time (and rightly so)