Thank you very much for the fast, clear, and detailed answer :)
On Fri, 1 Nov 2019 at 15:08, Ian Lance Taylor wrote:
> On Fri, Nov 1, 2019 at 6:31 AM Tom Payne wrote:
> >
> > cgo is often used to provide bindings to C libraries. Any memory
> allocated in the C library is not visible to Go, so G
On Fri, Nov 1, 2019 at 6:31 AM Tom Payne wrote:
>
> cgo is often used to provide bindings to C libraries. Any memory allocated in
> the C library is not visible to Go, so Go does not have an accurate view of
> the program's memory usage and does not run the garbage collector or any
> finalizers
cgo is often used to provide bindings to C libraries. Any memory allocated
in the C library is not visible to Go, so Go does not have an accurate view
of the program's memory usage and does not run the garbage collector or any
finalizers often enough. Consequently, memory usage for a Go server t
