Open Bug 1035403 Opened 10 years ago Updated 2 years ago

onsignalingstatechange closed event is missing after long call

Categories

(Core :: WebRTC, defect, P4)

Product:
Core
Component:
WebRTC
Platform:
x86_64
Linux
Type:
defect

Tracking

()

Blocking Flags:
backlog webrtc/webaudio+

People

(Reporter: drno, Unassigned)

Details

(Whiteboard: [webrtc-mochitest]) 

In our QA lab setup the mochitest test_peerConnection_basicAudioVideoCombined_long.html does not receive any onsignalingstatechange events when it closes the call after 3 hours. We this test failure message in the logs:
  Closing PeerConnections timed out
The same test code with the short call test_peerConnection_basicAudioVideoCombined.html receives the event just fine.
Might be a problem with the test or the actual implementation.
Whiteboard: [webrtc-mochitest]
backlog: --- → webRTC+
Rank: 35
Priority: -- → P3
Mass change P3->P4 to align with new Mozilla triage process.
Priority: P3 → P4
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.