1308921 - Multiple JS errors while waiting for peer to join conversation via Jitsi

Status: NEW

(Core :: WebRTC, defect, P5)

Description

[Cristian Comorasu, QA [:ccomorasu], Releae Desktop QA - Please contact [e-mail]]

[Affected versions]:

 Fx 50.0b5

[Affected platforms]:
 
 Windows XP x86
 Windows 7 x64
 Windows 8.1 x86
 Windows 10 x64

[Steps to reproduce]:

 1. Open Firefox
 2. Open a room via https://meet.jit.si/.
 3. Open the console (F12).
 5. Start a conversation with a peer. 

[Expected result]:

 The conversation starts without any issues.

[Actual result]:

 While waiting for the peer to join the conversation the JS errors :  "uncaught exception: undefined" increase by the second.

Comment 1

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

It appears from this report that the call establishes without any problem.  Errors in the console are minor if there's no user/app impact; and in this case may well be due to a bug in the site.  

Also: does this happen if full_duplex is off?

Comment 2

[Cristian Comorasu, QA [:ccomorasu], Releae Desktop QA - Please contact [e-mail]]

(In reply to Randell Jesup [:jesup] from comment #1)
> It appears from this report that the call establishes without any problem. 
> Errors in the console are minor if there's no user/app impact; and in this
> case may well be due to a bug in the site.  
> 
> Also: does this happen if full_duplex is off?

The errors occur with "media.navigator.audio.full_duplex" on true and false. One simpler way to see the errors is using " https://talky.io/  ". Here we can control the waiting time until the peer connects.
However these errors do not affect the conversation.

Comment 3

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

suggestions on finding the source of the exceptions?

Comment 4

[Jan-Ivar Bruaroey [:jib] (needinfo? me)]

I was able to reproduce with talky.io.

This is really a script error at this point. Open the JS debugger and set some breakpoints. I see tons of setTimeouts in the code. Pity our developer console can't locate where this particular exception is coming from, but someone with familiarity with the code should be able to recognize where an error of this high frequency must be coming from. Once it's been located to come from a platform call, or even a particular part of the content script, please include that info and let us know.

Comment 5

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

Likely should be closed, unless a developer from jitsi or talky can point to something we're doing wrong.

Comment 6

[Cristian Comorasu, QA [:ccomorasu], Releae Desktop QA - Please contact [e-mail]]

I am not a developer, nor do I know one for talky.io or jitsi.