#34865: DatabaseWrapper are not GC and connections are not closed
-------------------------------------+-------------------------------------
Reporter: Fábio Domingues | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 4.2
(models, ORM) |
Severity: Normal | 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 Carlton Gibson):
> ...I'd like to check out the patch proposal.
Yes, please.
Any chance you could give a minimal example showing the behaviour here, to
look at?
Various folks have reported ''leaky'' behaviour on Channels/Daphne, but
we've not been able to pin it down.
> … ends up in a circular reference ... and the GC could not cleanup the
objects.
Just out of interest, could you try throwing in a `gc.collect()` — that
**should** get it (but `WeakRef` is hopefully right in this case.)
--
Ticket URL: <https://code.djangoproject.com/ticket/34865#comment:4>
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/0107018abccd24cc-a453c7c0-c88a-4f5c-9121-d4ac3341b64b-000000%40eu-central-1.amazonses.com.
