MaxPending gives decrease number

[LeGamerDc]

Observed behavior

i run a benchmark of nats

func BenchmarkNatsT(b *testing.B) {
	nc, _ := nats.Connect("nats://127.0.0.1:4222", nats.ErrorHandler(func(nc *nats.Conn, sub *nats.Subscription, err error) {
		if errors.Is(err, nats.ErrSlowConsumer) {
			pm, pb, _ := sub.Pending()
			mpm, mpb, _ := sub.MaxPending()
			logger.Info("slow consumer", zap.Int("pending", pm), zap.Int("pendingBytes", pb),
				zap.Int("maxPending", mpm), zap.Int("maxPendingBytes", mpb))
		}
	}))
	sub, _ := nc.SubscribeSync("test")
	go func() {
		for i := 0; i < b.N; i++ {
			assert.Nil(b, nc.Publish("test", []byte("hello")))
		}
	}()
	for i := 0; i < b.N; i++ {
		_, _ = sub.NextMsg(time.Second)
	}
	pm, _, _ := sub.Pending()
	mpm, _, _ := sub.MaxPending()
	lpm, _, _ := sub.PendingLimits()
	fmt.Printf("%d/%d/%d\n", pm, mpm, lpm)
}

and see slow consumer log says pending=65536 and maxPending=65537. but, when benchmark ends, it give a mpm=6169, doesn't the maxPending should give biggest number in whole run?

Expected behavior

maxPending in the ends give 65537

Server and client version

nats-server --version
nats-server: v2.10.7

github.com/nats-io/nats.go v1.31.0 // indirect

Host environment

Mac with M1

Steps to reproduce

go test -bench=. -run=BenchmarkNatsT -count=1 -benchtime=1000000x