Test Condition

• Nighly on macOS 78.0a1 (2020-05-17) (64-bit)
• Open https://meet.google.com
• Start a meeting (you don't need any other people)
• Wait for 30-60 seconds

Expected Result

• Google Meet should work

Actual Result

• Google Meet exists, showing a screen with the message "Couldn't start the video call because of an error."
• The DevTools Error Log shows this:

RTCPeerConnection.getLocalStreams/getRemoteStreams are deprecated. Use RTCPeerConnection.getSenders/getReceivers instead. m=A7fCU,AJ9SK,AePfdf,BVgquf,CBlRxf,COQbmf,CvtcN,Cw0Hjd,DCwKHe,DM8swd,DNsE7e,EFQ78c,FMq9Lb,FYCkde,Fl2dbf,GkRiKb,HDvRde,HLo3Ef,Hn5sxd,I6YDgd,IZT63,Ivl8bd,JNoxi,JyyTHf,KG2eXe,L1AAkb,MI6k7c,MdUzUe,MsyKad,N5Lqpc,NNJERe,NpD4ec,O4tzsb,O6y8ed,OmgaI,PGW6ue,PQaYAf,PrPYRd,QBFzrf,QIhFr,QQnX0,RMhBfe,RoOsrd,RqS4qe,Ryzncf,SF3gsd,SdcwHb,SpsfSb,Tj958c,Tnlgmf,U0aPgd,Uas9Hd,UcHKNb,UgAtXe,V3dDOb,VwDzFe,W4cEdc,WO9ee,XAzchc,XU5LFb,XVMNvd,XxnxR,Y0bgVb,ZfAoz,ZwDk9d,ZxDaqc,a9EW5e,aW3pY,aurFic,azqyEc,bcHMGf,blwjVc,c6KVyc,cLFsDc,cWjcJb,cilABe,dWHZee,dodICd,e5qFLc,elYK3d,fFdwef,fHcPI,fKUV3e,fgj8Rb,gVaDd,hKSk3e,haHVHe,hc6Ubd,he,hl,iTsyac,iWP1Yb,jKHFJb,k2r0oe,kjKdXe,lAg79c,lPKSwe,lazG7b,llTWPd,lwddkf,mI3LFb,ma,mdR7q,nALW6c,o02Jie,obLw,pB6Zqd,pGAJif,pjICDe,pw70Gc,qexExd,qsafrb,rE6Mgd,rHjpXd,rNa50e,rn9YO,rrm,rsr,s39S4,sPwFo,swpmp,syIdOe,t8N1l,texUgd,tfTN8c,tgTcU,tlbU5,u4OpLc,w9hDv,wGFfpe,ws9Tlc,x60fie,xGC4Gb,xQtZb,xiqEse,y4Nztd,yDVVkb,zXsoW,zbML3c:1999:116

WebRTC: onaddstream is deprecated! Use peerConnection.ontrack instead. m=A7fCU,AJ9SK,AePfdf,BVgquf,CBlRxf,COQbmf,CvtcN,Cw0Hjd,DCwKHe,DM8swd,DNsE7e,EFQ78c,FMq9Lb,FYCkde,Fl2dbf,GkRiKb,HDvRde,HLo3Ef,Hn5sxd,I6YDgd,IZT63,Ivl8bd,JNoxi,JyyTHf,KG2eXe,L1AAkb,MI6k7c,MdUzUe,MsyKad,N5Lqpc,NNJERe,NpD4ec,O4tzsb,O6y8ed,OmgaI,PGW6ue,PQaYAf,PrPYRd,QBFzrf,QIhFr,QQnX0,RMhBfe,RoOsrd,RqS4qe,Ryzncf,SF3gsd,SdcwHb,SpsfSb,Tj958c,Tnlgmf,U0aPgd,Uas9Hd,UcHKNb,UgAtXe,V3dDOb,VwDzFe,W4cEdc,WO9ee,XAzchc,XU5LFb,XVMNvd,XxnxR,Y0bgVb,ZfAoz,ZwDk9d,ZxDaqc,a9EW5e,aW3pY,aurFic,azqyEc,bcHMGf,blwjVc,c6KVyc,cLFsDc,cWjcJb,cilABe,dWHZee,dodICd,e5qFLc,elYK3d,fFdwef,fHcPI,fKUV3e,fgj8Rb,gVaDd,hKSk3e,haHVHe,hc6Ubd,he,hl,iTsyac,iWP1Yb,jKHFJb,k2r0oe,kjKdXe,lAg79c,lPKSwe,lazG7b,llTWPd,lwddkf,mI3LFb,ma,mdR7q,nALW6c,o02Jie,obLw,pB6Zqd,pGAJif,pjICDe,pw70Gc,qexExd,qsafrb,rE6Mgd,rHjpXd,rNa50e,rn9YO,rrm,rsr,s39S4,sPwFo,swpmp,syIdOe,t8N1l,texUgd,tfTN8c,tgTcU,tlbU5,u4OpLc,w9hDv,wGFfpe,ws9Tlc,x60fie,xGC4Gb,xQtZb,xiqEse,y4Nztd,yDVVkb,zXsoW,zbML3c:2003

HTTP “Content-Type” of “text/html” is not supported. Load of media resource https://meet.google.com/ failed. yxx-kodn-eoj

I'm seeing this as well. Pretty sure it worked last week. I joined a meeting with a number of other partipicants and the meeting seemed to work initially.

Yep, it's brand new. It worked the last week. And the video still works, but I've got this after 2-3 min of running.

Can you find out the regression range (using mozregression)?

For the record: My nightly just upgraded to 78.0a1 (2020-05-18) and the issue still occurs.

[Tracking Requested - why for this release]: Google Meet no longer works in Firefox.

I'm able to reproduce this on Windows, but not mac for some reason.

Regression range:

• 2020-05-18T12:57:57.079000: INFO : Narrowed integration regression window from [4ca082ad, 170cb6b6] (3 builds) to [4ca082ad, 09a18345] (2 builds) (~1 steps left)
  2020-05-18T12:57:57.089000: DEBUG : Starting merge handling...
  2020-05-18T12:57:57.090000: DEBUG : Using url: https://hg.mozilla.org/integration/autoland/json-pushes?changeset=09a18345c269a8dddf7513e67f59fc20bc06f56f&full=1
  2020-05-18T12:57:57.921000: DEBUG : Found commit message:
  Bug 1632489 - Only adjust valid capture times when generating padding; r=bwc

Differential Revision: https://phabricator.services.mozilla.com/D75528

2020-05-18T12:57:57.921000: DEBUG : Did not find a branch, checking all integration branches
2020-05-18T12:57:57.925000: INFO : The bisection is done.
2020-05-18T12:57:57.928000: INFO : Stopped

Sorry I meant to set assignee to assignee of regressing bug, not reviewer.

Update: I am able to repro on mac after all. Pilot error on my part.

Just noticed Dan is on PTO starting today. We should probably just back this out. Byron WDYT?

As discussed in #media we'll turn off the just-added media.peerconnection.video.use_rtx for now to fix this.

https://hg.mozilla.org/mozilla-central/rev/6bc5897f488a

I updated my Nightly to latest just now but this was still happening. Turned it to false in about:config resolved it. Meet works again :)

I am on Nightly 78.0a1 (2020-05-21) and things work perfectly. Thanks for the quick fix!

-Henrik

It also works here. Thank you. 🥳

I'm trying to repro this in order to fix it from Meet's end, but have been largely unsuccessful on Linux, and completely unsuccessful on Mac. I see that there was pilot error in reproducing this on Mac earlier; could you detail the process you used to successfully repro this on Mac?

My attempts have looked like this thus far:

• Used Nightly build 80.0a1 (2020-07-08) 64-bit
• Ensured media.peerconnection.video.use_rtx is set to true
• Set media.peerconnection.video.use_rtx.blocklist to an empty string
• Started a video call between the Nightly browser and a Chrome browser
• No error occurs (Mac) / Video call disconnect happens, but very rarely (Linux)

I'm not able to repro on mac any longer for what it's worth (including blocklist steps in comment 19).

Sorry, I don't recall what my pilot error was in comment 5, but it was something unexciting like testing a wrong version of Firefox.

Dan, was something fixed here? Is it worth trying a reverse mozregression?

I noticed it working and thought it had been fixed on Meet's end. I am planning to remove *.google.com from the blocklist in Bug 1651722.

The only fix in this area lately was in Bug 1646092. There was a problem where Chrome was not accepting Firefox's SDP when there was no video device present on the Firefox side. I've noticed that when I join a call with Meet, I'm prompted for Microphone and Camera and then Camera again. If we end up in a state where we generated SDP with only the microphone present, maybe that caused problems with Meet too.

It is now working with a build from before Bug 1646092 landed, so that couldn't have been it.

As per comment 17, and 18, can the flag be updated to verified as well?

Best,
Clara

Yes