Hello,
I have posted a well detailed issue here on StackOverflow (it can be improved if asked): https://stackoverflow.com/questions/60972577/django-postgres-memory-leak - I have a custom command that crunches jobs coming from a Postgresql table jobs. - Since the command is multi threaded the action of “picking up the job” (select oldest job with status ‘pending’ && setting status to ‘in progress’) was made atomic. - The jobs I’m executing for this test are empty methods so the leak can’t be there. - Using tracemalloc pip package, I tracked down the python file and line that is allocating memory without ever relasing it: postgresql/operations.py:222 (Django 2.0.0) - I also installed Django 3 thinking that could have been an old bug but even with this update the problem is still there: postgresql/operations.py:235 (Django 3.0.5) - Please help. Thanks FM -- You received this message because you are subscribed to the Google Groups "Django users" 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/django-users/05c2ecda-95de-469d-977a-d0410df8899c%40googlegroups.com.
