Driver running out of memory

[BernhardFuchs]

In order to better manage the infrastructure, we introduced ResourceLimits to 512mb Ram on the Kubernetes cluster running the DIF resolver under dev.uniresolver.io

Atm the dock-did-driver is crashing with following error:

<--- Last few GCs --->

[51:0x7f137a924310]    78797 ms: Mark-sweep 246.9 (258.4) -> 245.7 (257.9) MB, 1269.7 / 0.0 ms  (average mu = 0.052, current mu = 0.002) allocation failure scavenge might not succeed
[51:0x7f137a924310]    78808 ms: Scavenge 246.7 (257.9) -> 245.7 (257.9) MB, 7.6 / 0.0 ms  (average mu = 0.052, current mu = 0.002) allocation failure
[51:0x7f137a924310]    78884 ms: Scavenge 246.7 (257.9) -> 245.8 (258.2) MB, 72.5 / 0.0 ms  (average mu = 0.052, current mu = 0.002) allocation failure


<--- JS stacktrace --->

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
error Command failed with signal "SIGABRT".
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

It is regularly restarted by Kubernetes schedule mechanism and then running for a few moments but most often did:dock is not resolvable.

[cykoder]

Interesting issue, thanks for pointing that out. Not sure exactly why the RAM usage is so high. Is there a limit you are able to set it to whereby it doesnt crash? Curious if its a leak or just caused by the extensive libs used (polkadotjs primarily)