Some memory leak is happening

[kamleshsahu]

Seems like some memory leak is happening. Using V3 branch, Started with `npm start` without any other configuration. Need help :)

[warren-bank]

Off-hand, I can't imagine what would cause this. I've never run into any CPU or RAM issues, but I've also never used the proxy in a production environment. I'm going to cross-reference this issue with another, which also has similar observations.

Either myself, or someone else, will need to run some kind of software to profile usage.. that can identify exactly which block of code within hlsd.js is responsible for the excessive usage.

My first question would be: what command-line options do you use when you start the proxy?

update: I've added some scripts to the repo that simplify the task of running the Node.js built-in profiler, applying some load on the proxy server, and then processing the raw log file to produce a log file that provided good insight. Unfortunately, the trivial load applied by this script doesn't produce any performance issues; nearly all of the CPU cycles are spent performing regex operations.. as would be expected. But.. it's a starting point…

[Phunky]

I’ve just stumbled upon this myself, I’m running via a simple docker container and it gobbled up as much RAM as it could without any streams hitting the proxy.

I’ll keep an eye on my logs and see if I can provide any insight into what maybe happening.