Bug: Memory Leak in signer service

[TorstenStueber]

The signer service has a memory leak caused by initiating new connections via polkadot-js.

This already happens in the status endpoint. The status endpoint opens the following connections and queries on-chain data:

• to Stellar
• to Pendulum
• to Moonbeam

Through experiments I can conclusively say that the connections to Stellar and Moonbeam via their respective libraries do not cause memory leaks and allow that all their allocated space can be cleanly garbage collected.

However, each call to sendPendulumStatusWithPk causes about 12 MByte of heap allocation that is not eligible for garbage collection.

TODO

Find a way to avoid the memory leak.

[TorstenStueber]

Seems like memory leaks in polkadot.js are well-known and not resolved. What a shame.

Also upgrading to polkadot-js 14.1.1 as suggested in one of the comments doesn't help.