[Django] #34865: DatabaseWrapper are not GC and connections are not closed

[Django]

#34865: DatabaseWrapper are not GC and connections are not closed
-------------------------------------+-------------------------------------
Reporter: domingues | Owner: nobody
Type: Bug | Status: new
Component: Database | Version: 4.2
layer (models, ORM) |
Severity: Normal | Keywords:
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
I have found possible memory leak when investigating why database
connections where not closed after the thread/coroutine ended
(https://code.djangoproject.com/ticket/33497 and
https://github.com/django/django/pull/17275), the `DatabaseWrapper` ends
up in a circular reference with
`DatabaseFeatures`/`DatabaseCreation`/`DatabaseClient`/... and the GC
could not cleanup the objects.
I tryed use `WeakRef` from the "child" objects to the wrapper or deleting
the `__dict__` and the wrapper was collected and the connections was
closed.

--
Ticket URL: <https://code.djangoproject.com/ticket/34865>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

[Django]

#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:
| Unreviewed
Has patch: 0 | Needs documentation: 0

Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------

Changes (by Fábio Domingues):

* Attachment "databasewrapper.png" added.

[Django]

#34865: DatabaseWrapper are not GC and connections are not closed
-------------------------------------+-------------------------------------
Reporter: Fábio Domingues | Owner: nobody

Type: Bug | Status: closed

Component: Database layer | Version: 4.2
(models, ORM) |

Severity: Normal | Resolution: duplicate

Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------

Changes (by Mariusz Felisiak):

* status: new => closed
* resolution: => duplicate

Comment:

Fabio, thanks for the report. Is there a reason to open a new ticket and
don't add your findings in the #33497? As far as I'm aware, this is a
duplicate.

--
Ticket URL: <https://code.djangoproject.com/ticket/34865#comment:1>

[Django]

#34865: DatabaseWrapper are not GC and connections are not closed
-------------------------------------+-------------------------------------
Reporter: Fábio Domingues | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 4.2
(models, ORM) |
Severity: Normal | Resolution: duplicate
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------

Comment (by Fábio Domingues):

Replying to [comment:1 Mariusz Felisiak]:

> Fabio, thanks for the report. Is there a reason to open a new ticket and
don't add your findings in the #33497? As far as I'm aware, this is a
duplicate.

Fixing this memory leak will not solve the problem of the persistent
connections not been reuse, only the fact that they will not pill up (and
starve the DB) if inaccessible.
But I'm new here, still learning. Should I move the findings to #33497?

--
Ticket URL: <https://code.djangoproject.com/ticket/34865#comment:2>

[Django]

#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
-------------------------------------+-------------------------------------

Changes (by Mariusz Felisiak):

* cc: Carlton Gibson, Andrew Godwin, Andreas Pelme (added)
* status: closed => new
* resolution: duplicate =>
* stage: Unreviewed => Accepted

Comment:

We can keep this separately.

Tentatively accepted, I'd like to check out the patch proposal.

--
Ticket URL: <https://code.djangoproject.com/ticket/34865#comment:3>

[Django]

#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]

#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 Fábio Domingues):

Tested using Uvicorn and Daphne, the database engine should not matter, I
tested with PostgreSQL, `CONN_MAX_AGE` could be any value and the effect
is the same using ''async'' or ''sync'' views.

{{{#!python

get_refs = lambda: [o for o in gc.get_objects() if isinstance(o,
BaseDatabaseWrapper)]
plot_refs = lambda: objgraph.show_backrefs(get_refs(), filename="sample-
graph.png")

def sync_view(request):
MyModel.objects.count()
# gc.collect()
# plot_refs()
return HttpResponse(f"Number of BaseDatabaseWrapper instances:
{len(get_refs())}")

async def async_view(request):
await MyModel.objects.acount()
# gc.collect()
# plot_refs()
return HttpResponse(f"Number of BaseDatabaseWrapper instances:
{len(get_refs())}")
}}}

On each refresh you should see the number of instances increase. If you
plot the references you would see many diagrams like the one in the
attachment. Throwing `gc.collect()` actually get it, but it take some
milliseconds, even if the underlying database connection is already
closed.

--
Ticket URL: <https://code.djangoproject.com/ticket/34865#comment:5>

[Django]

#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
-------------------------------------+-------------------------------------

Changes (by Fábio Domingues):

* Attachment "fix_34865.patch" added.

Possible approach

--
Ticket URL: <https://code.djangoproject.com/ticket/34865>

[Django]

#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 Fábio Domingues):

One more detail. Using `objgraph.show_growth` without doing `gc.collect`
give us this on each new request:
{{{
list 1990 +10
dict 6798 +3
deque 20 +2
lock 43 +2
OrderedDict 11 +2
partial 24 +2
ReferenceType 3848 +1
DatabaseWrapper 6 +1
DatabaseClient 6 +1
DatabaseCreation 6 +1
DatabaseFeatures 6 +1
DatabaseIntrospection 6 +1
DatabaseOperations 6 +1
BaseDatabaseValidation 6 +1
DatabaseErrorWrapper 5 +1
PGconn 5 +1
Connection 5 +1
PrepareManager 5 +1
AdaptersMap 7 +1
TypesRegistry 7 +1
}}}
with the previous patch the output of `show_growth` is empty.

--
Ticket URL: <https://code.djangoproject.com/ticket/34865#comment:6>

[Django]

#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
-------------------------------------+-------------------------------------

Changes (by Fábio Domingues):

* Attachment "fix_34865.patch" removed.

Possible approach

--
Ticket URL: <https://code.djangoproject.com/ticket/34865>

[Django]

#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
-------------------------------------+-------------------------------------
Changes (by Fábio Domingues):

* Attachment "fix_34865.patch" added.

Possible approach.

[Django]

[Django]

#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
-------------------------------------+-------------------------------------
Changes (by Fábio Domingues):

* Attachment "fix_34865.patch" removed.

[Django]

#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
-------------------------------------+-------------------------------------

Changes (by David Wobrock):

* cc: David Wobrock (added)

--
Ticket URL: <https://code.djangoproject.com/ticket/34865#comment:7>

[Django]

#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
-------------------------------------+-------------------------------------

Changes (by Priyank Panchal):

* owner: nobody => Priyank Panchal
* status: new => assigned

--
Ticket URL: <https://code.djangoproject.com/ticket/34865#comment:8>

[Django]

#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]

#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: 1 | Needs documentation: 0

Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------

Changes (by Sarah Boyce):

* has_patch: 0 => 1

--
Ticket URL: <https://code.djangoproject.com/ticket/34865#comment:10>

[Django]

#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: 1 | Needs documentation: 0

Needs tests: 1 | Patch needs improvement: 1

Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------

Changes (by Mariusz Felisiak):

* needs_better_patch: 0 => 1
* needs_tests: 0 => 1

Comment:

Marking as needs improvement per Florian's comment.

--
Ticket URL: <https://code.djangoproject.com/ticket/34865#comment:11>

[Django]

#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: 1 | Needs documentation: 0
Needs tests: 1 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------

Changes (by Florian Apolloner):

* cc: Florian Apolloner (added)

--
Ticket URL: <https://code.djangoproject.com/ticket/34865#comment:12>

[Django]

#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: 1 | Needs documentation: 0
Needs tests: 1 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------

Comment (by Patryk Zawadzki):

Florian, it does clean up ''eventually'' thanks to the garbage collection,
but garbage collection is a last resort method of freeing unused memory.

There are two important problems with relyin on GC:

1. It happens very rarely (the default thresholds are `(700, 10 10)`,
which means the deepest collection cycle—generation 2—only runs every
70,000 dereferenced objects. That's very rare; in a simple Django
application, that can mean a hundred requests.
2. It also locks the global interpreter lock and effectively freezes the
entire Python process (and all its threads) until it goes through all
uncollectable objects. The more objects it finds (not just the ones with
reference cycles but also everything else they hold a reference to), the
longer the freeze. In extreme cases, it can randomly add seconds to your
response times.

Aggregation of garbage leads to memory fragmentation as unused memory
cannot be reused until the garbage collection thresholds are met, which
leads to the overall memory use slowly creeping up.

What makes it worse is that in this case, it holds a reference to a
`psycopg` connection object, holding all of the psycopg internals hostage
and preventing proper finalization of the connection (and, I assume, in
Django 5.x also preventing the connection from being reclaimed by the
connection pool? I did not verify that).
--
Ticket URL: <https://code.djangoproject.com/ticket/34865#comment:13>

[Django]

#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: 1 | Needs documentation: 0
Needs tests: 1 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------

Comment (by Florian Apolloner):

Hi Patryk, I agree which is why this ticket is accepted. It just needs a
PR with tests (or an explanation why tests make no sense, are not
possible) and then we can see what we can do about that.

> What makes it worse is that in this case, it holds a reference to a
`psycopg` connection object, holding all of the psycopg internals hostage
and preventing proper finalization of the connection (and, I assume, in
Django 5.x also preventing the connection from being reclaimed by the
connection pool? I did not verify that).

I don't think so, the connection is not returned to the pool on GC but
rather when `.close` is called on it at the end of the request:
https://github.com/django/django/blob/5da3ad7bf90fba7321f4c2834db44aa920c70bc7/django/db/backends/postgresql/base.py#L391
--
Ticket URL: <https://code.djangoproject.com/ticket/34865#comment:14>

[Django]

#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: 1 | Needs documentation: 0
Needs tests: 1 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------

Comment (by Filip Owczarek):

Hi,
I just submitted my proposed solution.

https://github.com/django/django/pull/19153
--
Ticket URL: <https://code.djangoproject.com/ticket/34865#comment:15>

[Django]

#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: 1 | Needs documentation: 0
Needs tests: 1 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------

Changes (by Andreas Pelme):

* cc: Andreas Pelme (removed)

--
Ticket URL: <https://code.djangoproject.com/ticket/34865#comment:16>

[Django]

#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: 1 | Needs documentation: 0
Needs tests: 1 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------

Comment (by Florian Apolloner):

Thinking more about this ticket (please note that I am thinking out loud
here, so let me know if take a wrong turn somewhere): `DatabaseWrapper` is
in a standard setup *not* supposed to get garbage collected at all. Each
thread will have one wrapper per defined database stored in a thread local
(`ConnectionHandler`/`BaseConnectionHandler`). So unless the "web"server
is spawning a new thread per connection this should not be a problem (I
could see it being a problem for runserver but that is for dev only
anyways).

So to the people having issues here: Where exactly are you seeing this, in
job queues (celery etc) or in your webservers (which exactly). Fábio
mentioned seeing it on uvicorn / daphne, is this also a problem for
gunicorn (I know that one usually has a fixed worker & thread count
there).

Please note that I am not saying that there is no problem hidden here, the
cyclic reference is certainly ugly. But if the object isn't ment to get
garbage collected, it is not the end of the world. That said I would
certainly prefer a solution that doesn't use a weakref proxy (we would
need to do some profiling on the overhead).
--
Ticket URL: <https://code.djangoproject.com/ticket/34865#comment:17>

[Django]

#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: 1 | Needs documentation: 0
Needs tests: 1 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------

Comment (by Patryk Zawadzki):

Florian, we're using ASGI, so I believe it's very much spawning and
collecting threads left and right. The database wrapper-related objects
come up in garbage lists every few requests with `uvicorn` in production
mode.
--
Ticket URL: <https://code.djangoproject.com/ticket/34865#comment:18>

[Django]

#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: 1 | Needs documentation: 0
Needs tests: 1 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------

Comment (by Florian Apolloner):

Mhm yeah I recommended to switch to a fixed thread pool at some point iirc
:D Though even with a fixed thread pool I think that the "thread/asgi"
local might be per request then (ie async context id) which would show
this problem. Thank you for confirming that you are using ASGI.
--
Ticket URL: <https://code.djangoproject.com/ticket/34865#comment:19>

[Django]

#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: 1 | Needs documentation: 0
Needs tests: 1 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------

Comment (by Patryk Zawadzki):

Yeah, using a (cappable!) thread pool would be amazing, especially if the
async ORM API was also able to delegate to a request-specific DB thread
instead of mixing everything in a single shared thread.
--
Ticket URL: <https://code.djangoproject.com/ticket/34865#comment:20>

[Django]

#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: Ready for
| checkin

Has patch: 1 | Needs documentation: 0

Needs tests: 0 | Patch needs improvement: 0

Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------

Changes (by Florian Apolloner):

* needs_better_patch: 1 => 0
* needs_tests: 1 => 0
* stage: Accepted => Ready for checkin

--
Ticket URL: <https://code.djangoproject.com/ticket/34865#comment:21>

[Django]

#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: 1 | Needs documentation: 0

Needs tests: 1 | Patch needs improvement: 1

Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------

Changes (by Natalia Bidart):

* needs_better_patch: 0 => 1
* needs_tests: 0 => 1

* stage: Ready for checkin => Accepted

Comment:

I have updated the ticker per my review. I'm undecided whether we should
add a small release note highlighting this in case users are doing custom
resource cleanup and this gets in the way somehow...
--
Ticket URL: <https://code.djangoproject.com/ticket/34865#comment:22>

[Django]

#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: dev

(models, ORM) |
Severity: Normal | Resolution:

Keywords: | Triage Stage: Ready for
| checkin

Has patch: 1 | Needs documentation: 0

Needs tests: 0 | Patch needs improvement: 0

Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Natalia Bidart):

* needs_better_patch: 1 => 0
* needs_tests: 1 => 0
* stage: Accepted => Ready for checkin

* version: 4.2 => dev

--
Ticket URL: <https://code.djangoproject.com/ticket/34865#comment:23>

[Django]

#34865: DatabaseWrapper are not GC and connections are not closed
-------------------------------------+-------------------------------------
Reporter: Fábio Domingues | Owner: Priyank
| Panchal

Type: Bug | Status: closed

Component: Database layer | Version: dev
(models, ORM) |

Severity: Normal | Resolution: fixed

Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------

Changes (by nessita <124304+nessita@…>):

* resolution: => fixed
* status: assigned => closed

Comment:

In [changeset:"6a9db1e626952ffb37633586e6647319ea53467d" 6a9db1e]:
{{{#!CommitTicketReference repository=""
revision="6a9db1e626952ffb37633586e6647319ea53467d"
Fixed #34865 -- Released memory earlier than garbage collection on
database wrapping layers.

Thank you Florian Apolloner, Jake Howard and Patryk Zawadzki for
the clarifying comments and reviews.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/34865#comment:24>