Sidecar fails after reaching 4GB RSS Memory

[Imod7]

Description
A team using Sidecar has reported issues where the Sidecar processes gradually consumes up to 4Gb of RSS memory and then becomes incapable of handling any requests, requiring the process to restart. It's running in its own container alongside a Polkadot node. Despite allocating more resources to the container, it consistently fails once it hits the 4GB mark.

Linked to #1361

Possible Issues
Memory Leaks ?

Possible Good Resources

• Node.js Memory Limits - What You Should Know
• Node.js memory management in container environments

[filvecchiato]

While the container has more resources to allow Sidecar to run, if the process is not assigned a larger heap it would crash when the limit is reached. The start command could be modified to allow more heap memory (to match a larger container).

Some of the work done between PJS and Sidecar should allow it to run more efficiently so decreasing the likelihood to this specific case happening, however, more work is required to reduce the memory consumption. The PJS cache system will still be a big contributor to this issue.