Open hsorby opened 1 year ago
Since SWIG 4.1 the python bindings have been reporting a memory leak, we should look at refactoring the bindings to resolve this warning.
This appears to be a problem with SWIG not calling all Python packages to clean up their handles on close. Not sure if this is being dealt with. Need to have another look through SWIG PRs and issues.
Since SWIG 4.1 the python bindings have been reporting a memory leak, we should look at refactoring the bindings to resolve this warning.