1721963 - about:webrtc - packets received metric is wrongly reported as packets lost.

Status: VERIFIED FIXED

(Core :: WebRTC, defect)

Description

[[e-mail]]

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:90.0) Gecko/20100101 Firefox/90.0

Steps to reproduce:

1. Open any WebRTC application, e.g. v3demo.mediasoup.org in 2 tabs;
2. Open about:webrtc to monitor WebRTC metrics;
3. Observe RTP Stats metrics.

Actual results:

Packets lost metric exactly matches packets received metric, but media work fine.

Expected results:

Packets lost metric should reflect actual packets lost.

Comment 1

[[e-mail]]

Attachment: Bug 1721963 - Fixed packets lost metric in about:webrtc page. r=ng

Comment 2

[BugBot [:suhaib / :marco/ :calixte]]

The Bugbug bot thinks this bug should belong to the 'Core::WebRTC' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.

Comment 3

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/666ba1484b0c
Fixed packets lost metric in about:webrtc page. r=ng

Comment 4

[Natalia Csoregi [:nataliaCs]]

https://hg.mozilla.org/mozilla-central/rev/666ba1484b0c

Comment 5

[Monica Barbu]

Attachment: Screenshot_Fixed.gif

I was able to reproduce the issue on Nightly 92.0a1 (2021-07-23) (64-bit) (using W10 machine).
Issue is fixed on Beta 92.0b8 (64-bit) (using W10 machine).

But on Beta 92.0b8 build we saw an issue:

• 'about:webrtc' page is glitching (loading many times, see screenshot attached) when show details is pressed to view more details.
  Same issue is not reproducing on: OLD->Nightly 92.0a1 (2021-07-23) and Latest->Nightly 93.0a1 (2021-08-26) (64-bit).

Do you know anything about this new issue?

Comment 6

[[e-mail]]

Hi Monika. I don't know about new issue. The fix I've done was very tiny and only affected which number is reported as packets lost.

Comment 7

[Monica Chiorean]

Closing this as verified fixed on Win10, Mac 10.13 and Ubuntu 20.4 (95.0b5) and logged separate issue 1740679 for issue mentioned at comment 5.