Re: [webrtc-stats] Is keeping stats around a memory problem?

> If you add a new track, there may/will be a new trackstats object as well, but not an infinite number.

Say you `replaceTrack` to flip between front and back camera:

Every time trackA is removed, it leaves a new `detached` version. Every time it's added back, it creates a fresh track stats object (track stats are per attachment). There's no limit to how many times one can do this in JS. It's not so much the memory, rather `getStats` is already slow, and this might slow it down further over time. On ergonomics, this makes stats harder to parse correctly (need to process/filter out `detached` objects correctly to find recent data). See also https://github.com/w3c/webrtc-stats/issues/231.

-- 
GitHub Notification of comment by jan-ivar
Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/235#issuecomment-342383989 using your GitHub account

Received on Tuesday, 7 November 2017 05:59:40 UTC