After updating some jobs and republishing after the Dec 2024 release, I am getting an Out of Memory error on a job that runs a tRest API to pull data record by record. I am having to go through over 100,000 requests to the API. The job was running well, although long, before the update, but now it runs out of memory. I added more memory to the job but that just delays the out of memory error. I did a Memory Run and was able to watch as the memory would grow and get garbage collected and grow again and get garbage collected, but a little memory is not getting collected each cycle, so it builds until it blow.
I read somewhere on the internet in Talend docs about memory leaks now in tSetGlobalVar that is causing issues in long running ESB jobs. Since I am using tSetGlobalVar in this job design to hold onto statuses and set parameters for the API call, I am wondering if this is the problem. Could reassigning values to global variables be causing a memory build-up that eventually crashes the job?
Is anyone else experiencing this sort of issue with memory growing and not totally getting collected after taking updates to Talend Studio in recent months?
