Re:From Node.js to Go
by fighting on Tuesday May 17, 2016 @10:44AM
(#11714051)
They were more like things the go runtime was doing but which I had no clue or information about, rather than bugs. The top info was indeed rss.
[ Parent
| on HN ]
For me it seems like you probably leaked gorutines/not closed os resources or you encapsulated some data structures in themselves which then can't be garbage collected. It really looks like memory leak caused by app logic. But as i said you should report this if you are certain that is Go bug.