The DGraph.io team has a blog post about swapping to using jemalloc for CGo (they are going further and feeding their allocations into Go to avoid garbage collection, but that is a separate issue).
https://dgraph.io/blog/post/manual-memory-management-golang-jemalloc/ On Thursday, June 10, 2021 at 2:19:15 PM UTC-5 [email protected] wrote: > I'm using cgo and struggling to find a memory leak which can be easily > detected if I can replace the cgo memory allocator to the one the C library > I'm using have because they did a leak detector implementation there. > > It's possible? > > > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/2f582d3f-81bf-4863-8d36-dd09624d74b6n%40googlegroups.com.
