-
Notifications
You must be signed in to change notification settings - Fork 47
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
GoReplay v1.3.0_RC1 has goroutine leak when replaying traffic #926
Comments
I don't think this is a goroutine leak! the last stat(
|
I don't think so. Please read the Transport#dialConn function code. At the same time, go pprof can also show that a lot of goroutines is blocked on the readLoop and writeLoop functions. func (t *Transport) dialConn(ctx context.Context, cm connectMethod) (pconn *persistConn, err error) {
pconn = &persistConn{....}
// ......
go pconn.readLoop()
go pconn.writeLoop()
return pconn, nil
} |
@code4wt this is because the output HTTP code uses a single client with persist connection enabled! |
you are right, I have encountered this problem. error msg is as follows:
|
GoReplay stat log:

go ppref:

The text was updated successfully, but these errors were encountered: