Kui hangs shortly after startup

[NovemberZulu]

Describe the bug Kui hangs shortly after showing UI. Activity monitor shows 100% CPU use. This is a regression and/or broken config at my side, Kui used to work fine.

Steps to reproduce the behavior Start Kui from either Spotlight search or CLI kubectl-kui

Expected behavior Kui starts and runs normally

System

• Kui version: 12.0.3
• Operating system: macOS 12.5.1

[starpit]

thanks for the bug report! are you on Apple Silicon or Intel?

can you make sure to quit all open Kui processes (check the Dock for a Kui icon), and then:

DEBUG=* kubectl kui get pods 2> /tmp/kui.err

and attach that file here? also, if it works, could you try going to View -> Toggle Developer Tools, and see if there are any errors in the Consoel tab? if so, paste them here, too? thanks!

[NovemberZulu]

Thank you for getting back to me! I am on Intel. I wasn't able to go DevTools because I get the beachball of death and have to force quit Kui. I was able to see the result, though (no pods in default namespace) Here is the log. FInal lines lines look fishy. Is there a way to check what was that failed connection?

[starpit]

thanks! do you see the tray menu? if so, does it have any content? does it indicate version 12.0.3?

two more quick experiments:

1. this will disable the tray menu functionality altogether:

KUI_NO_TRAY_MENU=true kubectl kui get pods

2. this will attempt to run kui without popping up a window (kui isn't right now optimized for this flow; this is just to help with debugging):

KUI_HEADLESS=true kubectl kui get pods

[NovemberZulu]

I see tray menu, and is has reasonable content, and the version 12.0.3, even through the menu freezes as well.

KUI_NO_TRAY_MENU=true kubectl kui get pods works completely fine! No freezes, etc. I think we are getting closer to the root cause!

KUI_HEADLESS=true kubectl kui get pods briefly shows Kui icon in dock, and then it goes away.

[starpit]

excellent. so 1) you have a path now at least to use the latest version; and 2) yes, the bug seems to be in the tray menu logic. i'll add some more debugging hooks and do a code review. at the very least (i.e. short of us finding the bug), we will have more info if you want to try out the tray menu in the next build.

thanks again!

[starpit]

Oh, what version of kubectl do you have?

kubectl version

[NovemberZulu]

kubectl is 1.25.0, and clusters are 1.23.8. Could it be related?

[starpit]

those seem fine. but i'll do manual testing with the combo.

[k8s-triage-robot]

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:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.