Open Bug 1656263 Opened 4 years ago Updated 2 years ago

There are too many logs on about:webrtc page during a videocall on Cisco webex app

Categories

(Core :: WebRTC, enhancement, P3)

80 Branch
Desktop
All
enhancement

Tracking

()

Tracking Status
firefox79 --- affected
firefox80 --- affected
firefox81 --- affected

People

(Reporter: rpopovici, Unassigned)

References

(Blocks 1 open bug)

Details

Attachments

(1 file)

Attached image 2020-07-30_14h17_40.png (deleted) —

Note:

During a call with Cisco Webex Meetings, too many logs will appear on Session Statistics(12 logs).

Affected versions:

Nightly v81.0a1
Firefox 79.0
Firefox 80.0b1

Affected platforms:

all

Steps to reproduce:

  1. Load www.webex.com
  2. Click on "Sign Up now, it's free".
  3. Input an email address, input name, activate the account by the emailed link and set/create password.
  4. Go to meetingsemea25.webex.com, host a meeting and allow the microphone and camera permissions.
  5. Copy the meeting link (from the address bar) and load it on another system.
    Input a random name and email address and allow the microphone and camera permissions.
  6. Join the meeting.
  7. Admit the join request from the host system.

Expected result

There should be displayed a single log for that call on Session Statistics(about:webrtc)

Actual result

12 logs appear on about:webrtc page

Hardware: Unspecified → Desktop
Component: WebRTC: Audio/Video → WebRTC

We end up with one log entry per PeerConnection, not per call. So if you use a site like https://whereby.com where the connections are peer-to-peer and connection to two separate computers, you'll end up with two separate entries in the log, one for each PeerConnection. Ending up with all those logs on a webex call is because the site keeps creating new PeerConnections.

I agree this is pretty bad from a usability point of view, I've had difficulties figuring out what is going on with webex because of this. We probably want some way of grouping PeerConnections that are associated with a single call or a single tab together.

Blocks: 1624328
Severity: -- → S4
Type: defect → enhancement
Priority: -- → P3

We can also group PeerConnections that are never used to carry traffic, or have a checkbox to hide them, etc. IIRC most of these connections that Webex creates are never used. Grouping by "call" or tab won't really help for this case, though I think it is something we should do.

Just to be clear: the reason there are so many PeerConnections showing up on WebEx has been raised with Cisco a couple of times. WebEx appears to think that this results in better end user experience using these many, partially unused, PeerConnections.

You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: