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