-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JavaScript error in the main process: ECONNRESET TLSWrap.onStreamRead #8186
Comments
hello @eebomarsi , Thank you for contacting lens pro support ! I have reached out to our development team . |
+1 Hitting the same issue. Very annoying as the dialog box keeps popping up and does not even let you quit the application. |
Yeah I'm running in to this issue very often now as well |
Same issue with me as well. |
This is just plain crazy - i have to click >10 times on the error message since the last update!!! This app produces way over 100 error messages like this during the day ! Usually i just lock my macbook for some time and when i unlock it >10 messages like this one are waiting for me. A JavaScript error occurred in the main process Uncaught Exception: |
After last update i see less messages but they are still there. How to reproduce: lock your macbook, unlock - voila |
+1 This is very irritating, everytime you open lens there's bunch of OK button pending for you to resume work. ![]() |
Describe the bug
Ever since upgrading to Lens 2025:2:141554-latest (Electron: 33.4.0 Chrome: 130.0.6723.191 Node: 20.18.1), it hits a sequence of Javascript errors every few minutes:
A JavaScript error occurred in the main process
Uncaught Exception:
Error: read ECONNRESET
at TLSWrap.onStreamRead (node:internal/stream_base_commons:218:20)
To Reproduce
Steps to reproduce the behavior:
Just starting the new app with 3 clusters will cause the error. No user input needed.
Expected behavior
Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):
Logs:
When you run the application executable from command line you will see some logging output. Please paste them here:
Kubeconfig:
Quite often the problems are caused by malformed kubeconfig which the application tries to load. Please share your kubeconfig, remember to remove any secret and sensitive information.
Additional context
The text was updated successfully, but these errors were encountered: