Forcing Garbage Collection

[TIER1APP_YCRASH]

Is there a way to force the garbage collection ?

[iCFO]

Run Garbage Collector

I used this quite often years back. I will say that my earlier loop construction methods were occasionally sub-par, so I lean on it much less these days. Double check on how loops are being processed and closed out if that may be relevant to your workflows.

[takbb]

Hi @TIER1APP_YCRASH , as an example of advice re loops that @iCFO gave, see this post in which the OP did not actually need to collect the results of a loop, so instead could potentially replace the loop end with a variable loop end. This means the collected data is no longer needed and becomes inaccessible (de-referenced).

When the underlying java code finds that the collected data is “de-referenced” the (automatic) garbage collection should then be able handle the clean up more effectively.

Preventing "loop end node" to store all data

Hi @efegurtunca , if you don’t need the data from the loop, you can instead terminate the loop with a variable loop end node in place of the loop end node. Then just connect the flow-variable output port from Db Writer to the variable loop end. [image] For good measure, you could also include a java edit variable node, calling System.gc(); to suggest garbage collection occurs… [image] Hope that helps