Re:From Node.js to Go
by lossolo on Tuesday May 17, 2016 @10:55AM
(#11714156)
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.
[ Parent
| on HN ]
There are no comments on this comment yet.