OpenLens launches shell instances, running at 100% CPU which do not close on Lens close

[The-Judge]

Describe the bug When starting OpenLens and launching pod shells, multiple shell instances are started, which consume 100% CPU Load. These Shells also do not end once OpenLens is closed.

To Reproduce Steps to reproduce the behavior:

1. Start OpenLens
2. Connect to any cluster
3. Watch out for shell instances, consuming 100% CPU

Expected behavior I have no idea what these processes are doing. If this is legitimate processing, the least is to end these when OpenLens is closed and inform the user that legitimate activate is spawned in the background. Alternatively, do not make this happen at all.

Screenshots See demo here: https://youtu.be/ZbT7v8P1L9s

Environment (please complete the following information):

• Lens Version: 6.5.2-356
• OS: MacOS 13.4.1
• Arch: arm64 (M2)
• Installation method (e.g. snap or AppImage in Linux): Homebrew

Kubeconfig:

• Not related to a specific config
• Mine too large to share

Additional context Only way to get rid of the 100% CPU shells is to kill them individually.

[The-Judge]

Trying to hit the 1K?