Memory leak in Pleroma.Pool.Request
I have recently been getting memory allocation alerts when erlang pushes above 1GB of allocated memory, so I decided to take a look at the running processes
It seems that each Pool.Request process, sat in its idle state, is using an awful lot of memory.
Not quite sure what else I can do to debug this, but reporting it nonetheless
Edited by Sadposter