When one of several video elements using the same LocalMediaStream source is deleted, the remaining video elements freeze

RESOLVED FIXED

Status

()

Core
Audio/Video: Playback
RESOLVED FIXED
5 years ago
a year ago

People

(Reporter: Thomas Bruun, Unassigned)

Tracking

31 Branch
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

5 years ago
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/30.0.1599.101 Safari/537.36

Steps to reproduce:

1. Retrieve stream using getUserMedia
2. Create two <video> elements using the same stream
3. Remove one of the two elements from the DOM

Example: http://jsfiddle.net/Uxw2j/


Actual results:

The second video element freezes, displaying a frame from the stream before the first video element was removed.


Expected results:

The second video element should continue playing the stream. 

This also affects the stream being sent to other peers using RTCPeerConnection. User twi at #media was able to create a workaround by setting the src attribute of the video to be removed to something different, before removing the element.
(Reporter)

Updated

5 years ago
Component: Untriaged → WebRTC: Audio/Video
Product: Firefox → Core
(Reporter)

Updated

4 years ago
Version: 25 Branch → 31 Branch
Thank you for the report.
Confirmed the freeze in 31.0a1 (2014-04-11), Win 7 x64.
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Mac OS X → All
Hardware: x86 → All
(Reporter)

Comment 2

3 years ago
Our testing suggests this is fixed in Firefox 38.
Component: WebRTC: Audio/Video → Video/Audio
Component: Audio/Video → Audio/Video: Playback
Closing per comment 2.
Status: NEW → RESOLVED
Last Resolved: a year ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.