monokle consumes high resources

[yagilm]

Describe the bug
High CPU usage and memory filling up when running monokle. The environment feels slow and getting slower as time passes.

To Reproduce
Steps to reproduce the behavior:

1. Start Monokle
2. Observe resources usage

Expected behavior
Not running out of memory

Screenshots

Desktop (please complete the following information):

• OS: Linux Ubuntu 24.10
• Kernel Version: 6.11.0-21-generic
• Gnome (v. 47) on Wayland

[yagilm]

update:
It seems like this happens for clusters that use oidc-login for authentication.
So when connecting to the cluster I see in htop (up to the point my computer freezes) that many instances of the kubectl command is spawned. so kubectl oidc-login get-token --oidc-issuer-url=.....
This may mean that monokle doesn't cache the token ?
Note that the --cache flag was removed from kubectl since token caching is enabled by default (after ~ version 0.6), so, that may mean that monokle doesn't use the cached token under ~/.kube/cache/oidc-login/ ?

I would guess that different software can use the same cached token but also that the kubectl oidc-login get-token would happen only once even if another cache is used until the token is expired..