[Bug] Memory leak when using block handler without filter

Bug report

For the following subgraph we needed a way to initialize some values (at block 0):
https://github.com/Taraxa-project/taraxa-platform/tree/feature/add-subgraph-for-dpos/packages/dpos-subgraph

When we added a blockHandlers without a filter, it calls the handler for all blocks but the memory increases exponentially until the process is killed due to OOM.

The contents of the handler function doesn't matter. Also tested with an empty function.

Happens in Docker with v0.27.0, v0.28.0, v0.29.0, v0.30

https://user-images.githubusercontent.com/3051409/229186801-46673195-05fa-4f60-baa8-e2c636ee51e0.mp4

Relevant log output

No response

IPFS hash

No response

Subgraph name or link to explorer

No response

Some information to help us out

• Tick this box if this bug is caused by a regression found in the latest release.
• Tick this box if this bug is specific to the hosted service.
• I have searched the issue tracker to make sure this issue is not a duplicate.

OS information

Linux

Reproduziere den Bericht mit dem verknüpften dpos-subgraph, einem Block-Handler ohne Filter und graph-node v0.27.0 bis v0.30 in Docker unter Linux. Verfolge den Ausführungspfad des Block-Handlers und überprüfe, dass ein leerer Handler nicht mehr dazu führt, dass der Speicher wächst, bis der Prozess beendet wird.