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

$ go version
go version go1.17.6 darwin/amd64

Does this issue reproduce with the latest release?

Yes

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

Building for RHEL 7, on OS X MacOS Monterey 12.2.1

$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/abc/Library/Caches/go-build"
GOENV="/Users/abc/Library/Application Support/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOINSECURE=""
GOMODCACHE="/Users/abc/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="darwin"
GOPATH="/Users/abc/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/darwin_amd64"
GOVCS=""
GOVERSION="go1.17.6"
GCCGO="gccgo"
AR="ar"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD="/dev/null"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -arch x86_64 -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/pj/by4fdgcd4z159jc_l9hdws_r0000gn/T/go-build3032146476=/tmp/go-build -gno-record-gcc-switches -fno-common"

What did you do?

Create an HTTP/2 client using the net/http2 transport as below (I am using non-TLS/SSL connection to the HTTP/2 server) :

httpTransport = &http2.Transport{
					AllowHTTP: true,
					DialTLS: func(network, addr string, cfg *tls.Config) (net.Conn, error) {
						return net.Dial(network, addr)
					},
					StrictMaxConcurrentStreams: true,
				}

Multiple goroutines using the same http client (which uses this above transport), then attempt to send an HTTP POST request to the server. The number of goroutines attempting could be anywhere between 1000 to 10000 per second.

What did you expect to see?

Single TCP connection in the netstat output

What did you see instead?

Hundreds of TCP connections especially when the rate of invoking the http client is more than about 2000 per second.
I understand that this is related to #13397 for which a fix has apparently made it's way since Go 1.6.
But I am not sure why the number of TCP connections keeps growing to the order of hundreds.