runtime: threads and their Ms aren't released promptly enough in some case

[mayuehit]

What version of Go are you using (go version)?

$ 1.17

Does this issue reproduce with the latest release?

i don't know

What operating system and processor architecture are you using (go env)?

go env Output

$ go env
GOOS="linux"
GOPATH="/root/go"
GOVERSION="go1.17"
GOHOSTARCH="amd64"
GOARCH="amd64"

What did you do?

Use pprof find thread is more than goroutine

confirm the thread is 35 in os

It result in the memory increase caused by runtime.allocm and it is not released

What did you expect to see?

1、The number of threads decreases.
2、Memory growth caused by runtime.allocm no longer occurs

What did you see instead?

1、The number of threads is more than goroutine and not destroy.
2、Memory growth caused by runtime.allocm occurs

[mknyszek]

Does this reproduce with Go 1.18, Go 1.19, or at tip? For the record, Go 1.17 is no longer supported (https://go.dev/doc/devel/release#policy).

CC @golang/runtime

[mayuehit]

Does this reproduce with Go 1.18, Go 1.19, or at tip? For the record, Go 1.17 is no longer supported (https://go.dev/doc/devel/release#policy).

CC @golang/runtime

I dont know, maybe I could try use go 1.8 tomorrow to see if it still happen. I will report the result in 24 hours.

[mayuehit]

Does this reproduce with Go 1.18, Go 1.19, or at tip? For the record, Go 1.17 is no longer supported (https://go.dev/doc/devel/release#policy).

CC @golang/runtime

It reproduce with Go 1.18 @mknyszek