We have an web app for a streaming service. Whenever it streams the “Memory footprint” slowly grows until bove 1,000,000K as seen in the Tizen Task Metrics Manager.
Somewhere after that, the app crashes.
The heap size is around 25MB for the main thread, that handles the player and streaming and around 10-15 MB for the background worker (service-worker).
In the background-worker I see some objects with a much higher retained size than shallow size, like some webpack chunk loading and some tracking software. But I need to dig further into that.
Question: Doesn’t it sound like we have a leak, that fills up the memory and crashes the app? How exactly should we interpret “memory footprint”? Is it the current memory footprint of the browser running the app?
Any thoughts would be greatly appreciated.