Skip to content

ws-daemon go routine leak #3108

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

Closed
ArthurSens opened this issue Feb 4, 2021 · 5 comments · Fixed by #3824
Closed

ws-daemon go routine leak #3108

ArthurSens opened this issue Feb 4, 2021 · 5 comments · Fixed by #3824
Labels
component: ws-daemon type: bug Something isn't working type: needs triage We've seen the issue but need to investigate to decide what type of issue it is

Comments

@ArthurSens
Copy link
Contributor

Describe the bug

ws-daemon has go routine leaks, as shown by our monitoring data.

Go Routines:
image

Even though it looks strange that one pod is increasing a lot faster than the others, all pods are slowly (but steadily) increasing the number of go routines.

@ArthurSens ArthurSens added type: bug Something isn't working component: ws-daemon labels Feb 4, 2021
@aledbf
Copy link
Member

aledbf commented Feb 18, 2021

@ArthurSens do you know how to trigger the leak?

@ArthurSens
Copy link
Contributor Author

Sorry @aledbf, I don't have that information. We still need to investigate 🙁

@ArthurSens ArthurSens added the type: needs triage We've seen the issue but need to investigate to decide what type of issue it is label Feb 18, 2021
@aledbf
Copy link
Member

aledbf commented Apr 7, 2021

@ArthurSens I profiled the ws-daemon component in production and find out this is not a leak. Each workspace creates a goroutine for the daemon.sock socket file.

@ArthurSens
Copy link
Contributor Author

I'm not sure I understand how it explains it isn't a leak 🤔. The amount of goroutines is clearly increasing over time and will only go down after a restart. As you can see on the issue description, goroutines start at about a hundred and are only increasing as time passes. Reaching almost 500 avg in a week.

I just took another look at this same dashboard, and things are looking more troublesome after today's deployment!

A restart happened, so all leaked go routines dropped, but the increase rate is a lot higher now:
image

@ArthurSens
Copy link
Contributor Author

Maybe this graph from the EU cluster shows the difference better:

image

Amount of go routines are going to the roof after today's deployment

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component: ws-daemon type: bug Something isn't working type: needs triage We've seen the issue but need to investigate to decide what type of issue it is
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants