[Openmcl-devel] Tracking down a memory leak
ron at flownet.com
Sun May 30 17:21:41 PDT 2021
I have a long-running process that is slowly leaking memory over a period of days. I’ve tried tracking it down by intentionally running parts of the code in tight loops to see what makes the heap grow but no luck. AFAICT, all the code is well-behaved, and yet the memory image keeps growing inexorably so that I have to restart the process every couple of days. Does anyone have any ideas on how to track this down? Does the CCL GC have any secret internal diagnostics that might help?
More information about the Openmcl-devel