Javascript error in the main process

[galalmounir]

Describe the bug
With a pod selected, a random popup will appear with an uncaught exception

Screenshots

Environment:

• Lens Version: 5.0.1+20210705.1
• OS: MacOS

[Nokel81]

Do you have write permissions for ~/.kube?

[galalmounir]

Yes I do. This only started happening after the upgrade to v5

[Nokel81]

Okay thanks. I am trying to come up with a way to reproduce this issue on my machine. Because we don't try and read config.lock anywhere in our codebase I think it might be related to kubectl but I don't know enough about its internals yet.

[Nokel81]

Were you doing something in particular when this popup happened? For instance were you opening a local terminal instance?

[galalmounir]

I don't remember doing anything on the side. I'll try to repro again, but it keeps happening randomly.
Could it be related network connection/disconnection?

[Nokel81]

I have done some more reading and it could just be a race condition between two instances of kubectl running against the same config file.

[galalmounir]

Happened again this morning, this time my laptop was in sleep mode. Once I logged in, I found the same pop-up message.
After clicking Ok another message appeared:

[Nokel81]

That might be related to kube sync thanks for the report.

[guyguy333]

Having the same issue. It happens when I keep my computer running for night. Suddenly, fan speed increases, lens CPU usage is ~ 97% and there is a lock error.

A click on "Ok" results then in this error:

Finally, CPU usage decreases and it starts again few seconds later.

[Nokel81]

Sigh... JS's lack of event based tracing can sometimes be very annoying...

I have narrowed this to not being part of kube-sync because we do catch and log errors there.

[Nokel81]

Does this still happen?

[Nokel81]

I think that #3452 fixes this as we no longer try to read .lock files.