Skip to content

Memory leak in Kopf #664

Description

@nolar

Description

@vriesdemichael Hello. I am trying to investigate which version of Kopf, and maybe which specific commit causes the memory leak or failure in nolar/kopf#1172 (comment). Have you, by chance, managed to bisect the versions and figure out which one in particular causes it?

I have tried to reproduce the issue in my own clone of the operator with the integration tests only, but so far am failing on making it work with docker images — and I am not sure I can simplify/reduce the pipeline myself (I do not know what this operator does and what is Keycloak). UPD: I've made it run, all's good — I can bisect from here.

UPD: But I was unable to fail the tests. They do pass with kopf==1.42.3.

My goal was to bisect down to specific PRs and then commits by using the git notation of dependencies, like:

dependencies = [
  "kopf @ git+https://github.com/nolar/kopf.git@1234567890abcdef…"
]

That would really help to localise the issue. The diff 1.40.1 – 1.42.3 is too big, and I do not see what could cause the memory leaks so far.

Related: #446, #480, b386b91

Context

No response

AI Instructions

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions