Memory leak in Go http standard library?

http://stackoverflow.com/questions/21080642/memory-leak-in-go-http-standard-library

by ancarda • 13 years ago

10 7 13 years ago

mseepgood2• 13 years ago

https://groups.google.com/forum/#!forum/golang-nuts is the best place to ask Go related questions, not HN.

egeozcan• 13 years ago

I would argue that a serious memory leak in one of the core functions of such a popular and trending language is news worthy.

mseepgood2• 13 years ago

It's highly unlikely that there is a memory leak.

tptacek• 13 years ago

Stack Overflow questions with interesting answers are good bets for HN, but Stack Overflow questions about individual bugs with no answers aren't; they seem more like attempts to game Stack Overflow, and, at the very least, crud up HN. I actually flagged this.

ancarda• 13 years ago

I didn't think it would be interpreted that way. My bad. It seems like it's not a leak in the http library, just allocating memory and not releasing it sooner than expected.

regecks• 13 years ago

Go provides very adequate profiling tools for debugging this type of problem.

http://blog.golang.org/profiling-go-programs

FWIW, I did `ab -n 1million -c 100` with your program on Windows/amd64 and memory grew from from 3.4MB to 3.9MB.

Memory leak in Go http standard library?

Related Stories