#31373: Django 3.x / uwsgi is leaking connections
-------------------------------------+-------------------------------------
Reporter: Marcin Nowak | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 3.0
(models, ORM) |
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Andrew Godwin):
Oh, I missed the `runserver` comment - that would indeed indicate a severe
problem, as it uses bog-standard WSGI threading.
I suspect the problem will be with Local, as it is likely not precisely
replicating threading.local enough - working out how would be my line of
investigation. On the plus side, if it is that, we can ship a fix to
asgiref quickly out-of-cycle with Django and everyone will benefit.
I'd volunteer to look, but starting a new job and the current world
situation means I won't have time to do the investigation for a little
bit, but if we can trace it down to a direct behavioural difference I can
likely write the fix.
--
Ticket URL: <https://code.djangoproject.com/ticket/31373#comment:17>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.e85c4a010620d8d94b6be310e49e63b9%40djangoproject.com.
