Closed Bug 1542021 Opened 6 years ago Closed 6 years ago

NS_ERROR_UNEXPECTED from PeerConnection.jsm in signaling rollback demo

Categories

(Core :: WebRTC: Signaling, defect, P2)

defect

Tracking

()

RESOLVED FIXED
mozilla68
Tracking Status
firefox68 --- fixed

People

(Reporter: jib, Assigned: bwc)

References

Details

Attachments

(2 files)

STRs:

  1. Open https://jsfiddle.net/jib1/fqaeyx1h/62/
  2. Check ☐ Both noise
  3. Inside the iframe, uncheck ☑ Noise
  4. Uncheck ☑ Both noise

Expected result:
No error

Actual result:
6291 [Exception... "Unexpected error" nsresult: "0x8000ffff (NS_ERROR_UNEXPECTED)" location: "JS frame :: https://fiddle.jshell.net/_display/ :: onOff :: line 68" data: no]

Most likely from:

pc.removeTrack(button.sender);

Browser console shows:

NS_ERROR_UNEXPECTED: PeerConnection.jsm:1358
NS_ERROR_UNEXPECTED: PeerConnection.jsm:1184

It looks like this is happening because this test case tries to call replaceTrack on a stopped transceiver. We just aren't handling the error correctly.

Assignee: nobody → docfaraday
Pushed by bcampen@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/57ef4fc9dee8 Part 0: Check that removeTrack with a stopped transceiver doesn't throw an error. r=jib https://hg.mozilla.org/integration/autoland/rev/ca9b2ec29d98 Part 1: Check whether transceiver is stopped in removeTrack, and bail if so. r=jib
Created web-platform-tests PR https://github.com/web-platform-tests/wpt/pull/16519 for changes under testing/web-platform/tests
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: