W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > December 2020

[mediacapture-insertable-streams] Memory management of a frame once enqueued (#5)

From: youennf via GitHub <sysbot+gh@w3.org>
Date: Tue, 01 Dec 2020 14:44:02 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issues.opened-754456797-1606833840-sysbot+gh@w3.org>
youennf has just created a new issue for https://github.com/w3c/mediacapture-insertable-streams:

== Memory management of a frame once enqueued ==
Similarly to https://github.com/w3c/webrtc-insertable-streams/issues/49, it would be interesting to optimise the memory model of this API.
When JS receives a raw frame, it is convenient to have access to the frame pixels.
After JS enqueues the frame, the enqueued frame may be used for other purposes (some other JS processing for instance).
It might be best to detach at least the pixel data of the frame once processing is done (i.e. frame is enqueued).

Please view or discuss this issue at https://github.com/w3c/mediacapture-insertable-streams/issues/5 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:44:04 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:19:52 UTC