On Mon, Feb 24, 2025 at 9:20 AM Gavra <gav...@gmail.com> wrote: > I am not sure I understand. I have the issue reproducing only in production > on a running instance...
Not mentioned in the OP. You can still try to write tests and/or benchmarks that exhibit the same memory leak and then use them with the -memprofile facility. -- 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 golang-nuts+unsubscr...@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/golang-nuts/CAA40n-UBMeC9F_y4Dj4f4j-hWSPpUyG4EjXkzuxFnfRC-gszEA%40mail.gmail.com.
