[mediacapture-insertable-streams] Memory management for incoming frames (#6)

youennf has just created a new issue for https://github.com/w3c/mediacapture-insertable-streams:

== Memory management for incoming frames ==
In some cases, MediaStreamTrack might produce more frames than the JS pipeline might be able to consume.
In that case, it seems good that frames get dropped, for instance only the last frame received by the source is actually enqueued.

MediaStreamTrack may have different sources: camera, canvas, network.
Dropping frames might be ok with a camera since it will generate frames regularly.
This might be an issue for other sources like canvas where dropping a frame is visible to JS, as well as remote tracks (with webrtc stats).

That begs the question to whether different implementations should behave the same in the way they handle cases where frames get enqueued quickly.

Please view or discuss this issue at https://github.com/w3c/mediacapture-insertable-streams/issues/6 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Tuesday, 1 December 2020 14:51:15 UTC