Solved Surfer memory leak?

[robi]

The graphs seem to indicate something eating more resources over time.

It's not a busy site, and simply static pages.

[girish]

Most of the VMs like node.js won't garbage collect unless it reached a certain threshold/age and based on heap size. These are tunable using some command line options but 0.25GB is not very significant.

[nebulon]

Mostly in this case, nodejs will go up to the memory limit and only then trigger the garbage collection. This was one initial reason to add those memory limits as well, to make ruby/nodejs/... not go overboard.

So I don't think there is anything to solve here to be honest.

[robi]

Okay, it's a bit odd since that's the first time I've seen Surfer app crash due to this memory condition, presumably because the GC failed or was started too late with too little overhead available to complete.

Have tens of other Surfer apps that do not exhibit this behavior.