indexer-agent crash

<--- Last few GCs --->

[66493:0x5b962c0] 897845529 ms: Scavenge 3985.3 (4140.6) -> 3984.1 (4140.6) MB, 4.2 / 0.0 ms (average mu = 0.999, current mu = 0.999) allocation failure
[66493:0x5b962c0] 897845535 ms: Scavenge 3985.8 (4140.6) -> 3984.5 (4140.6) MB, 2.9 / 0.0 ms (average mu = 0.999, current mu = 0.999) allocation failure
[66493:0x5b962c0] 897846679 ms: Scavenge 3986.4 (4140.8) -> 3984.8 (4144.8) MB, 8.7 / 0.0 ms (average mu = 0.999, current mu = 0.999) allocation failure

<--- JS stacktrace --->

FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
1: 0xb06730 node::Abort() [node]
2: 0xa1b6d0 [node]
3: 0xce1dd0 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [node]
4: 0xce2177 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [node]
5: 0xe997e5 [node]
6: 0xea94ad v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [node]
7: 0xeac1ae v8::internal::Heap::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [node]
8: 0xe6d6ea v8::internal::Factory::NewFillerObject(int, bool, v8::internal::AllocationType, v8::internal::AllocationOrigin) [node]
9: 0x11e6456 v8::internal::Runtime_AllocateInYoungGeneration(int, unsigned long*, v8::internal::Isolate*) [node]

graph-indexer-agent --version
0.20.5-alpha.1

node -v
v16.18.0

Ubuntu 20.04.5 LTS

memory usage is growing all the time

Start by reviewing the reported graph-indexer-agent version, Node.js 16.18.0, and Ubuntu 20.04.5 environment, then reproduce the continuously growing memory usage using graph-indexer-agent. Investigate the process until it reaches the reported JavaScript heap limit; done means the agent no longer grows without bound during the reproduced workload.