Mike Brown
Mike Brown
`kubectl exec` or `crictl exec` cause goroutine and thus memory leak when using WebSocket connection
thx trying to pull in a few people to look at what happened here. https://github.com/kubernetes/kubernetes/issues/126608#issuecomment-2278120617
`kubectl exec` or `crictl exec` cause goroutine and thus memory leak when using WebSocket connection
@alfredkrohmer should be resolved with the next service patches... Thank you @dims.. very nice.
logs and version of kubernetes pls
from my read of the log ... for at least one of the issues: one issue is https://github.com/containerd/containerd/blob/main/pkg/cri/server/events.go#L389-L392 on task exit event notice ^ when handling we get a level=error...
@fuweid @mxpv thoughts?
> Maybe we should check the error for delete, just like kill. nod..
yeah a checkDeleteError and cover the extra cases sounds like a good idea!
possibly related lock contention associated with multiple parallel task execs PR: https://github.com/containerd/containerd/pull/8617 Note the part about "which could manifest as an exit event being published before a start event in...
another possibly related issue popped up https://github.com/containerd/containerd/issues/8698 with task exit event getting stuck in unmount
> > I think there may be a difference of opinion with regard to the point of view of the log being one of the root process tree or the...