Closed hariramshankar closed 1 year ago
Thank you for reporting this issue.
Will fix it later.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale
Any update on this? I experienced the same.
I'll find a cycle to fix it in a few days. Fix PRs from anyone are also welcome.
Hi,
I found a memory leak when calling kubeyaml_load_kubeconfig()
kubeyaml_load_kubeconfig creates a yaml parser object before attempting to read the kubeconfig file.
If opening the kubeconfig file failed for some reason, the function returns(-1) without freeing up the memory allocated to parser.
snippet of the code in question where the leak occurs