Code Leaks Memory on FreeBSD, but not on Linux about fasthttp HOT 4 CLOSED

Thank you for the response,

I believe you are correct with describing allocation being held on BSD vs Linux. Apologies for the non-issue.

from fasthttp.

I'm not sure how to help with this. There is no BSD specific code in fasthttp so I don't see how it could be causing this.

To me the FreeBSD memory profile looks more correct as it actually contains allocations you would expect. It seems like the Linux memory profile contains almost nothing which is unlikely. Try setting runtime.MemProfileRate = 1 at the top of your main func and re-run the memory profiles to get more accurate results.

Fasthttp will always keep some buffers allocated to re-use for next requests. You can see these in the FreeBSD profile but not in the Linux profile. Are you sure the Linux profile was made after it handled some requests?

Have you tried running the FreeBSD version for a while and see if the memory usage keeps increasing or if it stabilizes after a bit?

from fasthttp.

Thank you for your response,

Apologies for the previous Linux dump, this one with the MemProfileRate set is showing the Fasthttp buffers allocating as expected.

Versus FreeBSD, where the same test was done (same requests with the same body size amongst all of them)

It is also important to note that we use GoFiber (which uses fasthttp) for other endpoints, that do NOT have this issue when ran.

EDIT: On BSD, 45 minutes after all requests finished

from fasthttp.

It looks normal to me. I see buffers being allocated and kept. Why do you think there is a memory leak? What happens when you keep sending requests for a long time, does it run out of memory?

Your top screenshots show that Go has a lot of memory allocated. But that doesn't mean it's actually in use. If there is no memory pressure Go won't release memory to your system even if it isn't using any. How this behaves is differently between Linux and BSD I think.

from fasthttp.