Windows debug builds don't always start playing remote webrtc video after play() (race condition)

RESOLVED INCOMPLETE

Status

()

RESOLVED INCOMPLETE
5 years ago
3 years ago

People

(Reporter: jesup, Unassigned)

Tracking

22 Branch
x86_64
Windows 7
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [WebRTC] [blocking-webrtc-], URL)

(Reporter)

Description

5 years ago
With http://mozilla.github.com/webrtc-landing/pc_test.html, if you're running a windows debug build, remote video elements sometimes don't start - they'll stay blank, and when I hit 'Stop' they'll show a static frame (I think the first one).

If I change onaddstream() from doing video_element.play() to video_element.play(); setTimeout(video_element.play, 1000), then video starts reliably.

This implies there's a race condition in handling of play().

Note: it seems to be worse if I turn on various logging (signaling:5,webrtc_trace:65535) for example

It might be possible to happen in opt builds; it depends on what the timing issue is
Component: Audio/Video → WebRTC
(Reporter)

Updated

3 years ago
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.