Closed Bug 1441479 Opened 6 years ago Closed 1 year ago

Call gets frozen if closing the Firefox tab during a web.ciscospark call

Categories

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

defect

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox58 --- affected
firefox59 --- affected
firefox60 --- affected

People

(Reporter: emilghitta, Unassigned)

Details

(Keywords: cisco-spark, regressionwindow-wanted)

[Affected versions]:
Firefox 59b12 (BuildId:20180222170353)
Firefox 60.0a1 (BuildId:20180226230123)

[Affected platforms]:

Call between macOS 10.12 (Caller - Firefox Release) and Ubuntu 16.04 (Callee - Firefox Beta) via https://web.ciscospark.com/

[Steps to reproduce]:

1. The caller (A) performs a call to callee (B).
2. (B) answers the call.
3. (A) closes the Firefox call tab. 

[Expected result]:

The call is successfully ended.

[Actual result]:

(A)'s webcam is displayed as frozen to (B).


[Regression range]:
We will get back with a regression range asap.


NOTE: 
This issue was reproduced during a Nightly to Nightly call also.

This issue is also reproducible if (B) is performing step 3.

This is not reproducible with Google Chrome.
Can you please check if 58 is affected by this issue?

I'm asking because this might be caused by Cisco Spark not handling the changes implemented for the Transceiver work in Fx 59 properly.
Flags: needinfo?(emil.ghitta)
Keywords: cisco-spark
Hi Nils,

We retested this scenario by performing a call between Ubuntu 16.04 (Fx 58.0.2) and Windows 10 (Fx 58.0.2). It seems that this issue reproducible with 58 as well.
Flags: needinfo?(emil.ghitta)
Rank: 19
Priority: -- → P2
With it not being a recent regression I'm not sure how hard it will be to find a regression window.

The other question is if this is actually a bug in Firefox, or more a Cisco Spark issue in the sense that Spark appears to fail to recognize that one side of call just disapeared/crashed/... And it might be a problem which always existed with Cisco Spark.
Severity: normal → S3

Could not reproduce in Windows 10 - Ubuntu 22, Windows between Nightly v109.0a1 and Nightly v109.0a1.
Furthermore, this issue could not be attempted in the older versions, because the new app is not longer compatible with the old versions
Windows 10: the web app shows a blank dark-gray page in Nightly v58.0a1, V59.0a1 would load the main page, but it would give out an app error when a call was attempted.
Ubuntu 22: Nightly v58.0a1, v59.0a1, v60.0a1 -> v80.0a1 crash their tabs instantly and can't load anything, I suspect because of Wayland.
MacOS 11: Nightly v58.0a1, v59.0a1, v60.0a1 would not load anything in their tabs, only showing a blank content area.

Moreover, after 5 years, this application has been redesigned and its domain has changed as it redirects to web.webex.com. I believe this is safe to assume that this issue is no longer valid.

Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.