There seems to be a memory leak during MSE playback when using WPE 2.38.
During long term tests (24h playback) some applications reach their memory quota and WPEWebProcess is being killed.
The easiest way to reproduce the issue is to setup simple player on local HTTP server with below code:
<!DOCTYPE html>
<html>
<body>
<video id="v" controls autoplay muted style="width:100%; height:auto;"></video>
<script src="https://cdn.jsdelivr.net/npm/hls.js@latest"></script>
<script>
var url = "https://dwamdstream102.akamaized.net/hls/live/2015525/dwstream102/index.m3u8";
var video = document.getElementById("v");
if (Hls.isSupported()) {
var hls = new Hls({liveDurationInfinity: true});
hls.loadSource(url);
hls.attachMedia(video);
}
</script>
</body>
</html>During playback we can observe instant growth of WPEWebProcess memory:
This issue is also reproducible on Sagemcom reference platform.
Measurement is done using attached script (it checks VmRSS field every 5s in WPEWebProcess status).
rss_logger.sh
There seems to be a memory leak during MSE playback when using WPE 2.38.
During long term tests (24h playback) some applications reach their memory quota and WPEWebProcess is being killed.
The easiest way to reproduce the issue is to setup simple player on local HTTP server with below code:
During playback we can observe instant growth of WPEWebProcess memory:
This issue is also reproducible on Sagemcom reference platform.
Measurement is done using attached script (it checks VmRSS field every 5s in WPEWebProcess status).
rss_logger.sh