#34865: DatabaseWrapper are not GC and connections are not closed
-------------------------------------+-------------------------------------
Reporter: Fábio Domingues | Owner: Priyank
| Panchal
Type: Bug | Status: assigned
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 Florian Apolloner):
> Throwing gc.collect() actually get it, but it take some milliseconds,
even if the underlying database connection is already closed.
with "actually get it" do you mean that it cleans it up properly? If yes
there does not seem to be real leak here since garbage collection usually
runs every now and then (or do I miss something). It might still be
beneficial to improve the performance here but that might require a test
or two :D
--
Ticket URL: <https://code.djangoproject.com/ticket/34865#comment:9>
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018b00ebeb6e-065266a0-bfa6-4baf-a25b-b0d30635761e-000000%40eu-central-1.amazonses.com.
