Leaks in the Go standard library?

Question

go

The situation is almost identical to that described in this ticket: stackoverflow.com/questions/21080642/memory-leak-i...
I take the simplest code from the documentation:

package main

import (
    "net/http"
)

func main() {
    http.ListenAndServe(":8080", nil)
}

I run:

while [ true ]
do
    ab -n 1000 -c 100 http://127.0.0.1:8080/
    sleep 1
end

And I see how the program has more and more memory.
Damn, this is a standard example of the simplest library code call, how can this even be?
Who wrote web servers in Go, was it possible to do it without leaks using the standard library?

Answer 1

The first thing to check is the version of Go. early versions, even those that start with 1, are not particularly stable and suffer from leaks.
Secondly, you need to understand that keep-alive leaves connections open for some time and this affects the amount of memory consumed (however, when the activity becomes less, the memory will also be cleared over time). To make sure that it does not flow, it is worth disabling keep-alive for the test.